From: Felipe Contreras <felipe.contreras@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [PATCH] Standardize python shebangs
Date: Wed, 07 May 2014 14:06:16 -0500 [thread overview]
Message-ID: <536a842838fbb_76ff7a52ec5d@nysa.notmuch> (raw)
In-Reply-To: <vpqy4ydpiog.fsf@anie.imag.fr>
Matthieu Moy wrote:
> 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'.
> "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
next prev parent reply other threads:[~2014-05-07 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 10:03 [PATCH] Standardize python shebangs Felipe Contreras
2014-05-07 10:27 ` Johan Herland
2014-05-07 11:11 ` Felipe Contreras
2014-05-07 12:03 ` James Denholm
2014-05-07 12:28 ` Johan Herland
2014-05-07 18:06 ` Matthieu Moy
2014-05-07 19:06 ` Felipe Contreras [this message]
2014-05-07 20:23 ` Matthieu Moy
2014-05-07 20:40 ` Felipe Contreras
2014-05-07 20:57 ` Matthieu Moy
2014-05-07 22:19 ` James Denholm
2014-05-08 11:48 ` Matthieu Moy
2014-05-08 12:20 ` Johan Herland
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=536a842838fbb_76ff7a52ec5d@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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.
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).