From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Convert emailing part of hooks--update to hooks--post-receive
Date: Sun, 25 Mar 2007 02:13:04 -0700 [thread overview]
Message-ID: <7v7it54rfj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200703250951.04503.andyparkins@gmail.com> (Andy Parkins's message of "Sun, 25 Mar 2007 08:51:02 +0000")
Andy Parkins <andyparkins@gmail.com> writes:
> 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?
Surely.
As we discussed, I would prefer a patch to create this as a new
file in
contrib/examples/hooks/
directory. A single-liner
# see contrib/example/hooks for examples.
in another new file "templates/hooks--post-receive" would be
also nice.
>> 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.
and funny, isn't it?
> generate_email $2 $3 $1 | cat
>
> This is to force the deactivation of the pager for all the git commands
> that generate_email calls.
I think you could probably do the same with:
PAGER= generate_email "$2" "$3" "$1"
next prev parent reply other threads:[~2007-03-25 9:13 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 [this message]
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=7v7it54rfj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.