From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Todd Zullinger <tmz@pobox.com>, git@vger.kernel.org
Subject: Re: Git fails to detect subcommand when hook is symlinked to a builtin
Date: Sun, 20 Mar 2011 04:09:37 -0500 [thread overview]
Message-ID: <20110320090937.GA13167@elie> (raw)
In-Reply-To: <20110320082020.GA12663@elie>
Jonathan Nieder wrote:
> Instead, the rule is:
Sorry, that came out a muddle. Teemu Likonen explains the rule[1]
better. And Linus explains the rationale[2]. The main reason I found
this interesting enough to chime in is that I was considering
proposing changing the beginning of git scripts to
. "$(git --exec-path)/git-sh-setup"
to set a good example, which would be a regression in git's ability
to complain when used in a fragile way.
So, Todd: thanks for a very useful reminder.
[1] http://thread.gmane.org/gmane.comp.version-control.git/94378
[2] http://thread.gmane.org/gmane.comp.version-control.git/93825
prev parent reply other threads:[~2011-03-20 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 15:14 Git fails to detect subcommand when hook is symlinked to a builtin Todd Zullinger
2011-03-19 0:53 ` Junio C Hamano
2011-03-19 1:14 ` Todd Zullinger
2011-03-19 19:40 ` Junio C Hamano
2011-03-20 8:20 ` Jonathan Nieder
2011-03-20 9:09 ` Jonathan Nieder [this message]
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=20110320090937.GA13167@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tmz@pobox.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).