From: Junio C Hamano <gitster@pobox.com>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Taylor Blau <me@ttaylorr.com>,
Derrick Stolee <derrickstolee@github.com>
Subject: Re: [PATCH v3] format-patch: add --description-file option
Date: Mon, 21 Aug 2023 10:59:33 -0700 [thread overview]
Message-ID: <xmqqwmxop98a.fsf@gitster.g> (raw)
In-Reply-To: <20230821170720.577820-1-oswald.buddenhagen@gmx.de> (Oswald Buddenhagen's message of "Mon, 21 Aug 2023 19:07:20 +0200")
Oswald Buddenhagen <oswald.buddenhagen@gmx.de> writes:
> This patch makes it possible to directly feed a branch description to
> derive the cover letter from. The use case is formatting dynamically
> created temporary commits which are not referenced anywhere.
>
> The most obvious alternative would be creating a temporary branch and
> setting a description on it, but that doesn't seem particularly elegant.
>
> Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
> ---
The changed parts from the previous version all looked sensible.
Will replace and requeue.
Thanks.
next prev parent reply other threads:[~2023-08-21 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:09 [PATCH RESEND] format-patch: add --description-file option Oswald Buddenhagen
2023-08-08 6:33 ` Junio C Hamano
2023-08-09 17:15 ` [PATCH v2] " Oswald Buddenhagen
2023-08-11 21:38 ` Junio C Hamano
2023-08-11 22:29 ` Oswald Buddenhagen
2023-08-12 8:21 ` Junio C Hamano
2023-08-13 8:22 ` Oswald Buddenhagen
2023-08-21 17:07 ` [PATCH v3] " Oswald Buddenhagen
2023-08-21 17:59 ` Junio C Hamano [this message]
2023-08-21 22:05 ` Junio C Hamano
2023-08-23 20:01 ` Taylor Blau
2023-09-23 22:14 ` Kristoffer Haugsbakk
2023-09-25 19:01 ` Junio C Hamano
2023-09-25 19:29 ` Kristoffer Haugsbakk
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=xmqqwmxop98a.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=oswald.buddenhagen@gmx.de \
--cc=peff@peff.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).