Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Updates to git completion
- X-seq: zsh-workers 26480
- From: Nikolai Weibull <now@xxxxxxxx>
- To: Richard Hartmann <richih.mailinglist@xxxxxxxxx>
- Subject: Re: [PATCH] Updates to git completion
- Date: Thu, 29 Jan 2009 16:18:28 +0100
- Cc: Mikael Magnusson <mikachu@xxxxxxxxx>, Ingmar Vanhassel <ingmar@xxxxxxxxxxx>, "Zsh Hackers' List" <zsh-workers@xxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=dbSl+UOxT1j2iL4OhkRkc3/8xfMU/8RYcCtFrlVCjuI=; b=CrQABKtcep/kwzgfYf/aRvy43jediNHHiFONSvLKsYbYccGeev/1Xs5BpEX+2OwgXw HKLQ91TOX9/vJFptW7t5YGmmyHK/W3vFsqxYjdLG3xpWzBDcsB+eqgb5Y2EWGk2KG/c/ e0fEqoQ0GE80B17nIl6rdHtMZDsf1+yqrRn50=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=TSPoVaDIt1SLPgmSNH1F5Hv5KkDC61XBwebNcmoITdvczXeRdICoTRSXy/cP7DPeMc bvbX5YHGIynAEzQx+Jr7cTUY2p2JW5+jrGPwZ8p5FDe0MVDAcVSu3Bot+Zdxl7hAkPBG wBgtnKinyo6nEjHzzaP1xxywby9RaDhJsCmB8=
- In-reply-to: <2d460de70901290707m13032c77l782a8ca30ce09486@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <1233231710-1204-1-git-send-email-ingmar@xxxxxxxxxxx> <2d460de70901290636g6e0b43fw971397716cba8886@xxxxxxxxxxxxxx> <237967ef0901290640u9adf073g204586c1b290d0@xxxxxxxxxxxxxx> <2d460de70901290707m13032c77l782a8ca30ce09486@xxxxxxxxxxxxxx>
- Sender: nikolai.weibull@xxxxxxxxx
On Thu, Jan 29, 2009 at 16:07, Richard Hartmann
<richih.mailinglist@xxxxxxxxx> wrote:
> On Thu, Jan 29, 2009 at 15:40, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>> I think trying to complete options for the right versions for ~130
>> commands could make the
>> code just a bit convoluted and hard to follow. Not even git itself
>> documents when options
>> were introduced.
> Catch 22 :(
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author