git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "Michael Haggerty" <mhagger@alum.mit.edu>,
	"git discussion list" <git@vger.kernel.org>,
	"Sitaram Chamarty" <sitaramc@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Marc Branchaud" <mbranchaud@xiplink.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Chris Hiestand" <chiestand@salk.edu>
Subject: Re: [RFC v2] git-multimail: a replacement for post-receive-email
Date: Wed, 13 Feb 2013 15:26:57 +0000	[thread overview]
Message-ID: <201302131526.57342.andyparkins@gmail.com> (raw)
In-Reply-To: <vpqtxpgb6ue.fsf@grenoble-inp.fr>

On Wednesday 13 February 2013 14:56:25 Matthieu Moy wrote:
> Michael Haggerty <mhagger@alum.mit.edu> writes:

> I think adding a short "dependencies" section in the README (or in an
> INSTALL file) saying which Python version works could save new users the
> trouble (I see the sheebang inside the scripts says python2 but since I
> couldn't use my system's python and called
> "path/to/python git_multimail.py", this didn't help). Making the script
> portable with python 2 and 3 would be awesome ;-).

For my 2p worth, I don't like seeing hooks called like this.  Particular those 
that come as part of the standard installation.

I call mine by installing little scripts like this (on Debian):

  #!/bin/sh
  # stored as $GIT_WORK_DIR/.git/hooks/post-receive-email
  exec /bin/sh /usr/share/git-core/contrib/hooks/post-receive-email

This means I don't have to make the sample script executable, it gets upgraded 
automatically as git gets upgraded, and the interpreter is easily changed by 
changing a file in my work directory, rather than altering a packaged file.

I'd prefer to see the /usr/share/git-core/templates/hooks/ using a similar 
technique, as to my mind, installing a full copy of the sample script in every 
new repository is wasteful and leaves you with potentially out-of-date scripts 
when you update git.


Andy

-- 
Dr Andy Parkins
andyparkins@gmail.com

  reply	other threads:[~2013-02-13 15:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27  8:37 [RFC v2] git-multimail: a replacement for post-receive-email Michael Haggerty
2013-01-29 15:25 ` Ævar Arnfjörð Bjarmason
2013-01-30  2:27   ` Chris Hiestand
2013-02-13 14:56 ` Matthieu Moy
2013-02-13 15:26   ` Andy Parkins [this message]
2013-02-13 16:12     ` Matthieu Moy
2013-02-13 21:42   ` Michael Haggerty
2013-02-14 12:55     ` Matthieu Moy
2013-02-15  5:07       ` Michael Haggerty
2013-02-20 12:28 ` Matthieu Moy
2013-02-24  5:31   ` Michael Haggerty
2013-02-25  9:54     ` Matthieu Moy
2013-02-25 10:50       ` Michael Haggerty
2013-03-09  5:32         ` Michael Haggerty
2013-02-24  5:53   ` Michael Haggerty
2013-02-25 10:01     ` Matthieu Moy
2013-03-04  8:56   ` Matthieu Moy

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=201302131526.57342.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=avarab@gmail.com \
    --cc=chiestand@salk.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mbranchaud@xiplink.com \
    --cc=mhagger@alum.mit.edu \
    --cc=sitaramc@gmail.com \
    /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).