git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Peter Simons <simons@cryp.to>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] post-update.sample referenced obsolete binary "git-update-server-info"
Date: Tue, 21 Jul 2009 10:01:02 +0200	[thread overview]
Message-ID: <4A6575BE.6040308@drmicha.warpmail.net> (raw)
In-Reply-To: <87r5wb5s4o.fsf@write-only.cryp.to>

Peter Simons venit, vidit, dixit 20.07.2009 16:46:
> Hi Michael,
> 
>  >> -exec git-update-server-info
>  >> +exec git update-server-info
>  >>
>  >
>  > t/t5540-http-push.sh should fail if this really needed a fix (libexec
>  > is in $PATH for hooks).
> 
> you are right, the call to git-update-server-info does succeed, so there
> is no need to make that change.
> 
> Personally, I find it unfortunate, though, that those scripts rely on
> commands that won't exist when a normal user runs them.
> 
> Just my 2 cents,
> Peter
> 

Anyone can run them, just not from the default $PATH.

In fact, calling the dashed versions from the hooks is both safer and
(marginally) more efficient: Many people have several versions of git
lying around, and we've had more than one "bug" report where people
messed up because of mixing git bits from several versions. Calling the
dashed form above relies on the environment as set up by the caller, not
the user (who may have several "git" in $PATH, but not
"git-update-server-info"). Also, the command is called directly rather
than indirectly with "git" having to look for it.

Michael

  reply	other threads:[~2009-07-21  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 15:36 [PATCH] post-update.sample referenced obsolete binary "git-update-server-info" Peter Simons
2009-07-17 16:12 ` Michael J Gruber
2009-07-20 14:46   ` Peter Simons
2009-07-21  8:01     ` Michael J Gruber [this message]
2009-07-21 20:02       ` Peter Simons

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=4A6575BE.6040308@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=simons@cryp.to \
    /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).