From: Jan Hudec <bulb@ucw.cz>
To: Pascal Obry <pascal@obry.net>
Cc: Ping Yin <pkufranky@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: How to bypass the post-commit hook?
Date: Mon, 14 Jan 2008 18:59:51 +0100 [thread overview]
Message-ID: <20080114175951.GA5527@efreet.light.src> (raw)
In-Reply-To: <4778BB63.6080908@obry.net>
On Mon, Dec 31, 2007 at 10:50:27 +0100, Pascal Obry wrote:
> Jan Hudec a écrit :
> > By the way, what is your post-commit hook doing anyway? Modifying the work
> > tree *after* a commit does not sound like a common thing to do.
>
> Or just trigger a build via a built robot or record a commit information
> into an issue tracker...
That's not a case of "modifying a work tree *after* a commit".
There are many valid uses for post-commit hook and this is one of them. But
like the others it does not modify versioned files. That was the issue
discussed (and pre-commit indeed turned out a better match).
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
prev parent reply other threads:[~2008-01-14 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 15:12 How to bypass the post-commit hook? Ping Yin
2007-12-30 21:50 ` Jan Hudec
[not found] ` <46dff0320712302108i61f3b868obb93f89c1c24062c@mail.gmail.com>
2007-12-31 9:31 ` Jan Hudec
[not found] ` <46dff0320712310222m64d86e95l1499a7ffb1fff65c@mail.gmail.com>
2007-12-31 10:55 ` Jan Hudec
2007-12-31 13:26 ` Ping Yin
2007-12-31 17:05 ` Jan Hudec
2007-12-31 17:53 ` Ping Yin
2007-12-31 9:50 ` Pascal Obry
2008-01-14 17:59 ` Jan Hudec [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=20080114175951.GA5527@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
--cc=pkufranky@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).