Re: [PATCH] Standardize python shebangs

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 7, 2014, 19:06 UTC
Message-ID: <536a842838fbb_76ff7a52ec5d@nysa.notmuch>
In-Reply-To: <vpqy4ydpiog.fsf@anie.imag.fr>

Matthieu Moy wrote:

Show 7 quoted lines

> Felipe Contreras <felipe.contreras@gmail.com> writes:
> 
> > It's better if all our scripts use the same '/usr/bin/env python'.
> 
> Why?
> 
> Using python2 for git_multimail.py is a deliberate decision:

If you want to use python2, then use '/usr/bin/env python2'.

Show 9 quoted lines

> "The git-multimail project itself is currently hosted on GitHub:
> 
>     https://github.com/mhagger/git-multimail
> 
> We use the GitHub issue tracker to keep track of bugs and feature
> requests, and GitHub pull requests to exchange patches (though, if you
> prefer, you can send patches via the Git mailing list with cc to me).
> Please sign off your patches as per the Git project practice."
> )

If you are going to follow practices different than git.git, then multimail shouldn't live in 'contrib/'. Junio is already thretening to remove stuff out of contrib even when development behaves as the Git core does, so it makes more sense for stuff that doesn't.

-- 
Felipe Contreras