All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Michael Strawbridge <michael.strawbridge@amd.com>,
	 Douglas Anderson <dianders@chromium.org>,
	 git@vger.kernel.org,  entwicklung@pengutronix.de
Subject: Re: Regression: git send-email Message-Id: numbering doesn't start at 1 any more
Date: Wed, 08 Nov 2023 10:34:26 +0900	[thread overview]
Message-ID: <xmqqpm0l81ul.fsf@gitster.g> (raw)
In-Reply-To: <20231107070632.spe3cappk5b5jg3q@pengutronix.de> ("Uwe Kleine-König"'s message of "Tue, 7 Nov 2023 08:06:32 +0100")

Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:

> The output of git send-email dumps the messages it sends out and then I
> pick the message-id of the last mail by cut-n-paste and call my script
> with that as a parameter.

Yikes.  I was hoping that the whole "dumps the messages" output is
read by the script, so that it does not have to assume anything
about the Message-ID format (like "it has some unchanging parts,
the changing parts begin with 1, and it increments by 1 for each
message").

You could give Message-ID externally to the output of format-patch
before feeding send-email, which would just use them, and that way
you would have more control over the entire process, I guess.

  reply	other threads:[~2023-11-08  1:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 15:32 Regression: git send-email Message-Id: numbering doesn't start at 1 any more Uwe Kleine-König
2023-11-06 23:06 ` Junio C Hamano
2023-11-07  7:06   ` Uwe Kleine-König
2023-11-08  1:34     ` Junio C Hamano [this message]
2023-11-08 20:39     ` Michael Strawbridge

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=xmqqpm0l81ul.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=dianders@chromium.org \
    --cc=entwicklung@pengutronix.de \
    --cc=git@vger.kernel.org \
    --cc=michael.strawbridge@amd.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.