All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
Cc: "Oswald Buddenhagen" <oswald.buddenhagen@gmx.de>,
	"Jeff King" <peff@peff.net>, "Taylor Blau" <me@ttaylorr.com>,
	"Derrick Stolee" <derrickstolee@github.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v3] format-patch: add --description-file option
Date: Mon, 25 Sep 2023 12:01:01 -0700	[thread overview]
Message-ID: <xmqq7coet6vm.fsf@gitster.g> (raw)
In-Reply-To: <a1920050-bedc-49d4-840d-350b8fd3c003@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sun, 24 Sep 2023 00:14:28 +0200")

"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:

> On Mon, Aug 21, 2023, at 19:07, Oswald Buddenhagen wrote:
>> 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.
>
> Thanks for implementing this. I've just written cover letter text in
> separate files and copied them into the generated files every time. (I
> don't use branch descriptions.) I've wanted some convenient way to feed
> these messages in, and if I end up writing a cover letter again I'll most
> probably be using this new option.

Thanks for a positive feedback.  The changes is already in 'master'
since the beginning of this month or so and its way to be part of
the next release, I believe.



  reply	other threads:[~2023-09-25 19:01 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
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 [this message]
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=xmqq7coet6vm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=code@khaugsbakk.name \
    --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 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.