From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14444 invoked from network); 2 Feb 2009 18:53:13 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 2 Feb 2009 18:53:13 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 43403 invoked from network); 2 Feb 2009 14:49:09 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 2 Feb 2009 14:49:09 -0000 Received: (qmail 17504 invoked by alias); 2 Feb 2009 14:49:03 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26507 Received: (qmail 17486 invoked from network); 2 Feb 2009 14:49:02 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 2 Feb 2009 14:49:02 -0000 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by bifrost.dotsrc.org (Postfix) with ESMTP id 6780680271F0 for ; Mon, 2 Feb 2009 15:48:59 +0100 (CET) Received: by fg-out-1718.google.com with SMTP id l26so573160fgb.37 for ; Mon, 02 Feb 2009 06:48:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=X22uv3mBJ2OcJOXrLA+N9Wgfe0Jd3KZcBctJ7AQ7JzM=; b=QuQ7sgSeKbDFoIh3NW4OQVX3/1si9s8nP/aPchMcPlCPuflBwb9KpYF7qMtIN2Oz7E k0eP3yL0HYrchMVa57ieWZUrQAcidJPdo/J3zyCdCLIMznH+WcnnYomjEOF2fCzUv2w5 N+p3o7PyaOX5Ae7Fa96A+yfHCr5WH3mkmKmSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bJu/J7lXXL6AjgdWM0JLhMJ9YV0LmHfe3XR9yHNelusdsAISpbWKcCLZiEG30ZJ5fj Vmwy41Ym2GkxGOcNVIZhbPpcAmAc0ZlhninBBbwAjklETzQG/TD1/pQreSsOzCTpVoCC COfg8N5FBQ5VPcJlfg/7pOptZ44MbL2ZL5+/k= MIME-Version: 1.0 Received: by 10.86.97.7 with SMTP id u7mr147997fgb.8.1233586138690; Mon, 02 Feb 2009 06:48:58 -0800 (PST) In-Reply-To: References: <1233231710-1204-1-git-send-email-ingmar@exherbo.org> <2d460de70901290636g6e0b43fw971397716cba8886@mail.gmail.com> <237967ef0901290640u9adf073g204586c1b290d0@mail.gmail.com> <2d460de70901290707m13032c77l782a8ca30ce09486@mail.gmail.com> Date: Mon, 2 Feb 2009 09:48:58 -0500 Message-ID: Subject: Re: [PATCH] Updates to git completion From: Allan Caffee To: Zsh Workers Cc: Richard Hartmann , Mikael Magnusson , Ingmar Vanhassel , Nikolai Weibull Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.92.1/8940/Mon Feb 2 13:31:54 2009 on bifrost X-Virus-Status: Clean On Thu, Jan 29, 2009 at 10:18 AM, Nikolai Weibull wrote: > Yeah, that's way to complicated and adds even more complexity to an > already complex code-base (I should know, I wrote the initial commit). > One could follow upstream commits, but I found it easier to simply go > through the manual pages after each new (major) revision, adding new > options and removing old ones. This raises the question of why zsh is maintaining the completion for git at all. It would be simpler to match behavior with git's current version if they were tracked together. And git already tracks the bash completion. Thoughts? -Allan