From: "Josh England" <jjengla@sandia.gov>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] post-checkout hooks and related tests
Date: Wed, 26 Sep 2007 11:16:50 -0600 [thread overview]
Message-ID: <1190827010.6078.123.camel@beauty> (raw)
In-Reply-To: <7vve9y2v39.fsf@gitster.siamese.dyndns.org>
On Tue, 2007-09-25 at 16:17 -0700, Junio C Hamano wrote:
> "Josh England" <jjengla@sandia.gov> writes:
>
> > diff --git a/git-checkout.sh b/git-checkout.sh
> > index 17f4392..78355eb 100755
> > --- a/git-checkout.sh
> > +++ b/git-checkout.sh
> > @@ -137,6 +137,13 @@ Did you intend to checkout '$@' which can not be resolved as commit?"
> > git ls-files --error-unmatch -- "$@" >/dev/null || exit
> > git ls-files -- "$@" |
> > git checkout-index -f -u --stdin
> > +
> > + # Run a post-checkout hook -- the HEAD does not change so the
> > + # current HEAD is passed in for both args
> > + if test -x "$GIT_DIR"/hooks/post-checkout; then
>
> It is usually a good idea to view your patch in your MUA before
> sending them out.
>
> You will spot HT vs SP indentation inconsistencies right away.
Dang. It looked ok in emacs. :(
> HEAD did not change but don't you want to differenciate if the
> checkout was from the index or from the HEAD? If not why not?
Hmmmm. It wouldn't hurt to add another arg though I guess in case
someone might use it. I'm just trying to figure out how to word this
nicely in the Documentation.
-JE
prev parent reply other threads:[~2007-09-26 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 22:49 [PATCH] post-checkout hooks and related tests Josh England
2007-09-25 22:49 ` [PATCH] post-merge hook " Josh England
2007-09-25 22:49 ` [PATCH] Documentation for post-checkout and post-merge hooks Josh England
2007-09-25 23:21 ` [PATCH] post-merge hook and related tests Junio C Hamano
2007-09-25 23:17 ` [PATCH] post-checkout hooks " Junio C Hamano
2007-09-26 17:16 ` Josh England [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=1190827010.6078.123.camel@beauty \
--to=jjengla@sandia.gov \
--cc=git@vger.kernel.org \
--cc=gitster@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