From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 2/3] Only show log entries for new revisions in hooks--update
Date: Tue, 13 Feb 2007 18:08:17 +0000 [thread overview]
Message-ID: <200702131808.19291.andyparkins@gmail.com> (raw)
In-Reply-To: <7vbqjyymye.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2007, February 13, Junio C Hamano wrote:
> If we want to take this example hook seriously, I suspect that
> the existing mechanism based on hooks.* variables might need to
> be made to allow finer grained, per-branch, control. I dunno.
>
> Post 1.5.0.
Absolutely - per-branch sounds great. However, as that is definitely a
post-1.5.0 topic, I wanted to get the hook that was there in better
shape for the release.
Until the per-branch work is done, I think this patch is worth having.
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
prev parent reply other threads:[~2007-02-13 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 14:24 [PATCH 2/3] Only show log entries for new revisions in hooks--update Andy Parkins
2007-02-13 17:41 ` Junio C Hamano
2007-02-13 18:08 ` 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=200702131808.19291.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).