From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH v2] Reimplement emailing part of hooks--update in contrib/hooks/post-receive-email
Date: Sat, 31 Mar 2007 13:36:37 +0200 [thread overview]
Message-ID: <eulgu1$u2m$1@sea.gmane.org> (raw)
In-Reply-To: 200703302016.27303.andyparkins@gmail.com
Andy Parkins wrote:
> git rev-list --not --all
>
> would now give the wrong list because "--all" in the post-receive hook
> includes the ref that we are making the email for. This made it more
> difficult to show only the new revisions added by this update.
What about "git rev-list --not --all ^included" ?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-03-31 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 10:23 [PATCH] Convert emailing part of hooks--update to hooks--post-receive Andy Parkins
2007-03-24 12:43 ` Junio C Hamano
2007-03-24 15:44 ` Andy Parkins
2007-03-24 16:12 ` Linus Torvalds
2007-03-25 7:13 ` Junio C Hamano
2007-03-25 7:07 ` Junio C Hamano
2007-03-25 7:50 ` Junio C Hamano
2007-03-25 8:51 ` Andy Parkins
2007-03-25 9:13 ` Junio C Hamano
2007-03-30 19:16 ` [PATCH v2] Reimplement emailing part of hooks--update in contrib/hooks/post-receive-email Andy Parkins
2007-03-31 11:36 ` Jakub Narebski [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='eulgu1$u2m$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).