From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Bill Lear <rael@zopyra.com>, git@vger.kernel.org
Subject: Re: GIT v1.5.1-rc1
Date: Mon, 19 Mar 2007 22:55:39 -0400 [thread overview]
Message-ID: <20070320025539.GA28922@spearce.org> (raw)
In-Reply-To: <7v7itcd8mk.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Bill Lear <rael@zopyra.com> writes:
>
> > On Monday, March 19, 2007 at 03:53:47 (-0700) Junio C Hamano writes:
> >>...
> >>* Hooks
> >>
> >> - The sample update hook to show how to send out notification
> >> e-mail was updated to show only new commits that appeared in
> >> the repository. Earlier, it showed new commits that appeared
> >> on the branch.
> >
> > I did not see Shawn's changes to the update hooks in here, and can't
> > recall where these stand at the moment --- will these be forthcoming?
>
> Do you mean "[PATCH] Split sample update hook into post-receive
> hook"? My impression was that the discussion that followed made
> its interface obsolete with later 8-patch series from Shawn.
I think that's what Bill means, and you are correct Junio, that patch
is not valid anymore now that post-receive takes its data on stdin.
I was hoping Andy or one of the other folks who have worked on
that hook would pick up the ball and update the hook, but I
think they are stuck on the fact that you cannot use:
git log $new --not --all
in the post-receive hook to see what commits are "new to this
repository", as $new is already in --all. ;-)
That almost needs a --all-except="refs/heads/a refs/heads/b" option
to rev-list. Grrrr.
--
Shawn.
next prev parent reply other threads:[~2007-03-20 2:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 6:35 [PATCH] Make 'make' quieter while building git Shawn O. Pearce
2007-03-06 7:03 ` Junio C Hamano
2007-03-06 7:16 ` Shawn O. Pearce
2007-03-06 8:15 ` Junio C Hamano
2007-03-06 8:21 ` Shawn O. Pearce
2007-03-06 10:53 ` Short term release plans Junio C Hamano
2007-03-19 10:53 ` GIT v1.5.1-rc1 Junio C Hamano
2007-03-19 13:21 ` Bill Lear
2007-03-20 1:08 ` Junio C Hamano
2007-03-20 2:55 ` Shawn O. Pearce [this message]
2007-03-20 9:37 ` Andy Parkins
2007-03-20 14:42 ` Shawn O. Pearce
2007-03-20 23:30 ` Jakub Narebski
2007-03-21 5:06 ` Junio C Hamano
2007-03-21 16:07 ` Andy Parkins
2007-03-19 14:13 ` Johannes Schindelin
2007-03-20 1:04 ` Junio C Hamano
2007-03-20 1:19 ` Johannes Schindelin
2007-03-06 9:16 ` [PATCH] Make 'make' quieter while building git Alex Riesen
2007-03-06 13:24 ` Johannes Schindelin
2007-03-06 13:37 ` Alex Riesen
2007-03-06 14:19 ` Johannes Schindelin
2007-03-06 23:02 ` Junio C Hamano
2007-03-06 23:11 ` Alex Riesen
2007-03-06 23:24 ` Shawn O. Pearce
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=20070320025539.GA28922@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rael@zopyra.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).