git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Anton Gladkov <agladkov@parallels.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] [RFC] add Message-ID field to log on git-am operation
Date: Sun, 23 Mar 2008 11:32:08 -0700	[thread overview]
Message-ID: <7v4pax70lz.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080323171621.GA3886@atn.sw.ru> (Anton Gladkov's message of "Sun, 23 Mar 2008 20:16:21 +0300")

Anton Gladkov <agladkov@parallels.com> writes:

> On Sat, Mar 22, 2008 at 12:51:34PM -0700, Junio C Hamano wrote:
> ...
>> Wouldn't it work equally well to use applypatch-msg hook?  Use your
>> updated mailinfo to parse necessary information out of the incoming
>> message, and add Message-ID: to the commit log messsage, perhaps at the
>> end, in that hook?
>
> applypatch-msg hook executed on message applying, after that there could be
> useful to test applied patch, so it is not the place for notification sending.

And nobody suggested to send anything from the hook.

As I understood from your e-mail without proposed commit log message, your
assumed workflow was:

	receive mail
        "git am" it
	test rewrite amend whatever you want to convince yourself that
         the received patch was Ok
        push the result out
        pushed-into repository has a hook to send notification,
         by picking up the Message-ID from the commit object

The only thing you need was that the message-id information is available
somewhere in the commit object.  I objected to your patch that puts it in
the commit object header and suggested it be placed in the commit log
message.  You can implement such custom commit munging to add an extra
Message-ID: line inside the hook.  You do not have to send out e-mail nor
anything from it.

  reply	other threads:[~2008-03-23 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 22:00 [PATCH] [RFC] add Message-ID field to log on git-am operation Anton Gladkov
2008-03-22 19:51 ` Junio C Hamano
2008-03-23 17:16   ` Anton Gladkov
2008-03-23 18:32     ` Junio C Hamano [this message]
2008-03-24  6:43       ` Anton Gladkov

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=7v4pax70lz.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=agladkov@parallels.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).