From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Sam Vilain <sam.vilain@catalyst.net.nz>
Subject: Re: [PATCH] git-merge: run commit hooks when making merge commits
Date: Thu, 12 Jul 2007 09:03:44 +0100 [thread overview]
Message-ID: <200707120903.46538.andyparkins@gmail.com> (raw)
In-Reply-To: <7vd4yy4opa.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2007 July 11, Junio C Hamano wrote:
> The commit-msg hook I have no clue what people usually use it
> for in the real world, but a merge commit message tends to be
I use it for adding my Signed-Off-By automatically in my git repository. Of
course that's only valid for the likes of me because I can be sure that I
only ever commit my own patches, rather than integrating other people's.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
prev parent reply other threads:[~2007-07-12 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 10:32 [PATCH] git-merge: run commit hooks when making merge commits Sam Vilain
2007-07-11 21:26 ` Junio C Hamano
2007-07-11 23:21 ` Sam Vilain
2007-07-12 8:03 ` Andy Parkins [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=200707120903.46538.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sam.vilain@catalyst.net.nz \
/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).