From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Cc: Nikolai Weibull <now@bitwi.se>,
zsh-users@zsh.org, Clint Adams <clint@users.sourceforge.net>,
Doug Kearns <dkearns@users.sourceforge.net>,
Peter Stephenson <pws@users.sourceforge.net>
Subject: Re: Git completion - contributing to git.git
Date: Thu, 1 Jul 2010 11:35:01 +0200 [thread overview]
Message-ID: <AANLkTilvnDhLPU6kFb5sdOm4zilHQSeK0mroFITiFsi2@mail.gmail.com> (raw)
In-Reply-To: <20100701083302.GA5988@vidovic>
On Thu, Jul 1, 2010 at 10:33, Nicolas Sebrecht
<nicolas.s-dev@laposte.net> 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.
next prev parent reply other threads:[~2010-07-01 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 1:05 Nicolas Sebrecht
2010-07-01 8:00 ` Nikolai Weibull
2010-07-01 8:13 ` Richard Hartmann
2010-07-01 8:18 ` Nikolai Weibull
2010-07-01 8:33 ` Nicolas Sebrecht
2010-07-01 9:15 ` Nikolai Weibull
2010-07-01 9:32 ` Frank Terbeck
2010-07-01 9:35 ` Richard Hartmann [this message]
2010-07-04 5:50 ` Doug Kearns
[not found] ` <AANLkTin9y2_EtnBDYfdG1ctEHP3GkiStbXFMvf3GX3gp__29002.7882242159$1278224383$gmane$org@mail.gmail.com>
2010-07-04 8:45 ` Štěpán Němec
2010-07-04 9:58 ` Simon Ruderich
[not found] ` <20100704095831.GA14152__37531.721746973$1278237962$gmane$org@ruderich.org>
2010-07-04 12:09 ` Štěpán Němec
2010-07-01 8:19 ` Frank Terbeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilvnDhLPU6kFb5sdOm4zilHQSeK0mroFITiFsi2@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=clint@users.sourceforge.net \
--cc=dkearns@users.sourceforge.net \
--cc=nicolas.s-dev@laposte.net \
--cc=now@bitwi.se \
--cc=pws@users.sourceforge.net \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).