From: "Shawn O. Pearce" <spearce@spearce.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, Bill Lear <rael@zopyra.com>
Subject: Re: Git push failure with update hook success
Date: Thu, 8 Mar 2007 05:06:55 -0500 [thread overview]
Message-ID: <20070308100655.GG30289@spearce.org> (raw)
In-Reply-To: <200703081004.32666.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
> On Thursday 2007 March 08 09:28, Shawn O. Pearce wrote:
> > Andy Parkins <andyparkins@gmail.com> wrote:
> > > Without adding some nasty switches to git-rev-list
> > > (like --all-except-this-branch), I can't see how the post-update hook
> > > could ever send emails with the necessary amount of detail.
> >
> > Which is why `master` now has support for a post-receive hook,
> > that has the magic three parameters. ;-)
>
> It still won't work - what about the
>
> git-rev-list --not --all
>
> Problem?
>
> By the time that hook runs the master ref (for example) has changed,
> so "--not --all" includes the new revisions, and you get no output.
Dammit. That's so obvious. And I missed it.
I got nothing at this hour of the morning.
--
Shawn.
prev parent reply other threads:[~2007-03-08 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 16:29 Git push failure with update hook success Bill Lear
2007-03-07 16:46 ` Bill Lear
2007-03-07 17:09 ` Shawn O. Pearce
2007-03-07 17:25 ` Bill Lear
2007-03-07 17:38 ` Shawn O. Pearce
2007-03-07 23:09 ` Shawn O. Pearce
2007-03-07 23:15 ` Bill Lear
2007-03-08 9:22 ` Andy Parkins
2007-03-08 9:28 ` Shawn O. Pearce
2007-03-08 9:54 ` Junio C Hamano
2007-03-08 10:04 ` Andy Parkins
2007-03-08 10:06 ` Shawn O. Pearce [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=20070308100655.GG30289@spearce.org \
--to=spearce@spearce.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--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).