From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Convert emailing part of hooks--update to hooks--post-receive
Date: Sun, 25 Mar 2007 08:51:02 +0000 [thread overview]
Message-ID: <200703250951.04503.andyparkins@gmail.com> (raw)
In-Reply-To: <7vfy7tajiz.fsf@assigned-by-dhcp.cox.net>
On Sunday 2007, March 25, Junio C Hamano wrote:
> I think you can do something along the following line.
>
> (1) You say "for-each-ref --all" to get the ref information
> that is after update.
Would you mind if I delayed that to a separate patch? It's a
significant difference from the original update hook, so I think it's
worth having that change separately documented.
> Sorry, what I meant was:
>
> git show -s --pretty=oneline "$oldrev"
Ah - no problem. Done.
> Actually it was not quite "nicely done". If taggername has an
> unusual character then dq pair you hard coded there may not
> quote the string correctly.
Devious. Fixed as you suggest.
> > (Andreas Ericsson 54) prev=$(git describe "$3^" | sed
> > 's/-g.*//')
>
> You could describe all the parents and see if they differ. If
> they reach different tag, we could see which one is newer. Or
> something like that. In the special (but usual) case of a
> single parent commit, "describing all the parents" is what you
> are already doing, so it is not any more expensive in the normal
> case.
Again; I think I'll fix that one as a separate patch as it is a change
from the behaviour of hooks/update.
> Please do not have cat on either side of a pipe. That makes a
> shell script look ... eh, you know the word ;-).
>
> sed -e 1q "$GIT_DIR/description"
Done. I've taken the liberty of adding a pipe-to-cat, that I hope
you'll forgive...
# Output to the terminal in command line mode - if someone wanted to
# resend an email; they could redirect the output to sendmail themselves
generate_email $2 $3 $1 | cat
This is to force the deactivation of the pager for all the git commands
that generate_email calls.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-03-25 8:54 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 [this message]
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
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=200703250951.04503.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).