From: Junio C Hamano <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Subject: Re: [PATCH v2] send-email: relay '-v N' to format-patch
Date: Sun, 27 Nov 2022 10:25:01 +0900 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Kyle Meyer's message of "Sat, 26 Nov 2022 15:21:23 -0500")
Kyle Meyer <firstname.lastname@example.org> writes:
> Here's a patch handling the -v case. I don't plan on working on a more
> complete fix for the other cases (as I mentioned before, I don't use
> send-email to drive format-patch), but in my opinion the -v fix by
> itself is still valuable.
Yup, I think it is a good place to stop for the first patch. Other
people can add more when they discover the need, and anything more
complex [*] is probably not worth the effort, I would think.
Side note: [*] we could imagine running "git format-patch -h"
(or a new variant of it), parse its output and populate the
%options dynamically, for example.
Will queue. Thanks.
next prev parent reply other threads:[~2022-11-27 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 2:00 [PATCH] send-email: disable option auto-abbreviation Kyle Meyer
2022-11-25 7:11 ` Junio C Hamano
2022-11-25 17:31 ` Kyle Meyer
2022-11-26 20:21 ` [PATCH v2] send-email: relay '-v N' to format-patch Kyle Meyer
2022-11-27 1:25 ` Junio C Hamano [this message]
2022-11-28 12:34 ` Ævar Arnfjörð Bjarmason
2022-11-28 9:41 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).