From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-15138-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 3414 invoked by alias); 1 Jul 2010 08:33:16 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 15138
Received: (qmail 26943 invoked from network); 1 Jul 2010 08:33:14 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,FREEMAIL_FROM autolearn=ham version=3.3.1
Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.161.43 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:sender:date:from:to:cc
         :subject:message-id:references:mime-version:content-type
         :content-disposition:content-transfer-encoding:in-reply-to
         :user-agent;
        bh=U1zov27tpShhvet83urZd5vyGbuqCixIiO49VGIZJXg=;
        b=VFMhbWJGSxrxzhw/5rRWcDkU+4p0CHEX+hmwchj9k85IZ7kJ1Vi7vMmtGApoHGpFza
         iDzTc3pmc0hvRgcBWwNTgbL1sNcNZgEJ3c+O9YxE3YJoMTCTudWLH7KB3vMhjD/CjzA5
         EIZW9ZbMXTAp5avYMtl4to2wHapC8ZuGJeUPU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:date:from:to:cc:subject:message-id:references:mime-version
         :content-type:content-disposition:content-transfer-encoding
         :in-reply-to:user-agent;
        b=hoypRhQCJSp+zX8PYB+0LfCr4+7q16FtlW9zTmuoJrjeOuLpMeG7r8+AMOJXKkxkoS
         u4Y0XrSySsBTAzucqATVvDz7dfhIESEI32uJ3B77D/gj1QIFyxIXkQDM9PVASzobQ1ui
         MmG7deZojKWCsX/9lmrRHFryDuRNw/UE61ENw=
Sender: Nicolas Sebrecht <ni.s.nis33@gmail.com>
Date: Thu, 1 Jul 2010 10:33:02 +0200
From: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
To: Nikolai Weibull <now@bitwi.se>
Cc: Nicolas Sebrecht <nicolas.s-dev@laposte.net>, 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
Message-ID: <20100701083302.GA5988@vidovic>
References: <20100701010506.GC13062@vidovic> <AANLkTik6Ys8mRgMj8yz0Iyo5bUIXyqQFtZFqRFyXAF42@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <AANLkTik6Ys8mRgMj8yz0Iyo5bUIXyqQFtZFqRFyXAF42@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)

On Thu, Jul 01, 2010 at 10:00:42AM +0200, Nikolai Weibull wrote:
> 
> (Why am I not included in the Cc?  I am the original and principal
> author, after all.  The minuscule amount of attribution it would have
> provided would have been nice. ;-)

I'm sorry for that. I did a command like

  git blame -- path/to/_git | cut -d' ' -f2,3 | sort | uniq

on my Git's zsh repository which is obviously not approppriate. :-/

> I’d rather not, to be honest.  It’s always a pain to have two files,
> as they can become out of sync when patches are sent to one repository
> and not the other, users don’t know which version to use, and so on.

I believe this could easily be solved by versionning the file (yes,
by adding a "# vXYZ"). Perhaps a more explicit header could help :

  # vXYZ

  # If you intend to contribute to maintaining this file, please
  # increase the version number and fill the patches to both zsh and git
  # projects at <addresses>. Thanks!

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
.

Thoughts?

-- 
Nicolas Sebrecht