From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] svnrdump_sim: start the script with /usr/bin/env python
Date: Tue, 27 Nov 2012 23:36:38 -0800 [thread overview]
Message-ID: <7vy5hmgovt.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20121128025734.21231.47468.chriscool@tuxfamily.org> (Christian Couder's message of "Wed, 28 Nov 2012 03:57:33 +0100")
Christian Couder <chriscool@tuxfamily.org> writes:
> All the python scripts except contrib/svn-fe/svnrdump_sim.py
> start with "#!/usr/bin/env python".
>
> This patch fix contrib/svn-fe/svnrdump_sim.py to do the same.
I suspect you need a bit more than that.
$ make git-p4
$ diff -u git-p4.py git-p4
shows you how we tell the scripts how to find their interpreters
(that way, there is no need to rely on the existence of
/usr/bin/env).
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> contrib/svn-fe/svnrdump_sim.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/svn-fe/svnrdump_sim.py b/contrib/svn-fe/svnrdump_sim.py
> index 1cfac4a..d219180 100755
> --- a/contrib/svn-fe/svnrdump_sim.py
> +++ b/contrib/svn-fe/svnrdump_sim.py
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python
> +#!/usr/bin/env python
> """
> Simulates svnrdump by replaying an existing dump from a file, taking care
> of the specified revision range.
next prev parent reply other threads:[~2012-11-28 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 2:57 [PATCH] svnrdump_sim: start the script with /usr/bin/env python Christian Couder
2012-11-28 7:36 ` Junio C Hamano [this message]
2012-11-28 8:03 ` Felipe Contreras
2012-11-28 8:55 ` Christian Couder
2012-11-28 16:57 ` Junio C Hamano
2012-11-28 19:19 ` Felipe Contreras
2012-11-28 19:33 ` Junio C Hamano
2012-11-28 21:32 ` Felipe Contreras
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=7vy5hmgovt.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.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.
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).