Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Git completion - contributing to git.git
- X-seq: zsh-users 15141
- From: Richard Hartmann <richih.mailinglist@xxxxxxxxx>
- To: Nicolas Sebrecht <nicolas.s-dev@xxxxxxxxxxx>
- Subject: Re: Git completion - contributing to git.git
- Date: Thu, 1 Jul 2010 11:35:01 +0200
- Cc: Nikolai Weibull <now@xxxxxxxx>, zsh-users@xxxxxxx, Clint Adams <clint@xxxxxxxxxxxxxxxxxxxxx>, Doug Kearns <dkearns@xxxxxxxxxxxxxxxxxxxxx>, Peter Stephenson <pws@xxxxxxxxxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=vKAzyJzKwCvA+NlzxxTSf4tOvTLbs+rjBLywusIErtw=; b=eibQieYNhhn7HJ2oKcXN+/8tb/+aKuzMROo1ljT5iUmqnHH4JuY+ZCTkh9CaL2nyaR 6l0Dam3yOMeoR4l2emwNrtCTqxngIKh28Y6berfm/jFyGntecOjUISnRyvoc3bGyilsS R5wxhFNfQD08d7uHWm1L3DBiLE4PSFGPN9ldE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=QUQbHOxmGnjr2QsyogafeT+CbxbyxY1caOVzgFmxTsyUCKLJtG9iGO3Hy1VqCeLvsM OCC5WXDiD/JGwziYtUxiK6ge2OfOu8W14sFLQoMJfheqXAROu3TZIg4g/QZM6qokc0ig Ka9kXEesQBtfQRj4YE4GsaW6ogz8J2qVm6DxI=
- In-reply-to: <20100701083302.GA5988@vidovic>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <20100701010506.GC13062@vidovic> <AANLkTik6Ys8mRgMj8yz0Iyo5bUIXyqQFtZFqRFyXAF42@xxxxxxxxxxxxxx> <20100701083302.GA5988@vidovic>
On Thu, Jul 1, 2010 at 10:33, Nicolas Sebrecht
<nicolas.s-dev@xxxxxxxxxxx> wrote:
> The worst cases for me would be to either
> Âhave two unrelated zsh completion files in each project
> or
> Âmaintaining a public (possibly sent to the Git project) completion
> Âfile downstream to the zsh one
Who will take care of this? Will you still reliably follow through on
doing this in half a year? A year? Five years?
Unless you _really_ want to do that, we will end up with a split brain
at some point.
This is why I asked for automated stuff. You write it once and, unless
things change significantly, it keeps on working.
Richard
PS: Automation could be as easy as sending a full list of differing
commits to the other dev list every time something changes. Though that
should be OK'ed by pws for the git list and no idea who on git's side.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author