From: Eli Barzilay <eli@barzilay.org>
To: git@vger.kernel.org
Subject: Problem with contrib/hooks/post-receive-email
Date: Fri, 19 Mar 2010 02:39:02 -0400 [thread overview]
Message-ID: <m3vdcsq0hl.fsf@winooski.ccs.neu.edu> (raw)
The post-receive-email script goes out of its way to avoid sending
commits twice by filtering out commits that are included in existing
refs, but if more than one branch changes then some commits can end up
not being reported. For example, I made two commits A and B, made one
branch point at A and another at B, and pushed both -- neither of the
resulting two emails had A.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next reply other threads:[~2010-03-19 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 6:39 Eli Barzilay [this message]
2010-03-19 16:39 ` Problem with contrib/hooks/post-receive-email Andy Parkins
2010-03-19 18:44 ` Brandon Casey
2010-03-20 3:21 ` Eli Barzilay
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=m3vdcsq0hl.fsf@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--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).