From: Pete Harlan <pgit@pcharlan.com>
To: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Cc: Pete Harlan <pgit@pcharlan.com>
Subject: [PATCH v2 0/2] post-receive-email configurable rev display
Date: Mon, 3 Nov 2008 23:19:52 -0800 [thread overview]
Message-ID: <1225783194-24640-1-git-send-email-pgit@pcharlan.com> (raw)
In-Reply-To: <7v7i7kthkc.fsf@gitster.siamese.dyndns.org>
This is the second version of the user-configurable revision display
patch. The first version decreased the efficiency of the default
case, while this avoids it thanks to a suggestion by Junio.
The first version of this patch also failed to customize the display
of revisions included in newly-created branches; this version displays
those revisions in the same manner as for updated branches.
The two places (new vs. updated branches) where the original code
displayed revisions used similar code. The first patch in this series
factors that out to a separate routine that handles both cases, in
order to avoid duplicating the code introduced in the second patch.
Pete Harlan (2):
contrib/hooks/post-receive-email: Put rev display in separate
function
contrib/hooks/post-receive-email: Make revision display configurable
contrib/hooks/post-receive-email | 57 ++++++++++++++++++++++++++++++++------
1 files changed, 48 insertions(+), 9 deletions(-)
next parent reply other threads:[~2008-11-04 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7v7i7kthkc.fsf@gitster.siamese.dyndns.org>
2008-11-04 7:19 ` Pete Harlan [this message]
2008-11-04 23:55 ` [PATCH v2 0/2] post-receive-email configurable rev display Junio C Hamano
2008-11-04 7:19 ` [PATCH v2 1/2] contrib/hooks/post-receive-email: Put rev display in separate function Pete Harlan
2008-11-04 7:19 ` [PATCH v2 2/2] contrib/hooks/post-receive-email: Make revision display configurable Pete Harlan
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=1225783194-24640-1-git-send-email-pgit@pcharlan.com \
--to=pgit@pcharlan.com \
--cc=andyparkins@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