From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH 0/3] format-patch: teach --infer-cover-subject option
Date: Sun, 18 Aug 2019 22:37:31 -0400 [thread overview]
Message-ID: <cover.1566182184.git.liu.denton@gmail.com> (raw)
Currently, format-patch only puts "*** SUBJECT HERE ***" when a cover
letter is generated. However, it is already smart enough to be able to
populate the cover letter with the branch description so there's no
reason why it cannot populate the subject as well.
Teach format-patch the --infer-cover-subject and corresponding
format.inferCoverSubject configuration option which will read the
subject from the branch description using the same rules as for a commit
message (that is, it will expect a subject line followed by a blank
line).
Also includes some other cleanup along the way.
This was based on patches 1-3 of an earlier patchset I sent[1].
[1]: https://public-inbox.org/git/cover.1558492582.git.liu.denton@gmail.com/
Denton Liu (3):
t4014: clean up style
Doc: add more detail for git-format-patch
format-patch: infer cover letter from branch description
Documentation/config/format.txt | 5 +
Documentation/git-format-patch.txt | 35 +-
builtin/log.c | 56 ++-
t/t4014-format-patch.sh | 656 ++++++++++++++++-------------
4 files changed, 425 insertions(+), 327 deletions(-)
--
2.23.0.248.g3a9dd8fb08
next reply other threads:[~2019-08-19 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 2:37 Denton Liu [this message]
2019-08-19 2:37 ` [PATCH 1/3] t4014: clean up style Denton Liu
2019-08-19 16:02 ` Eric Sunshine
2019-08-19 2:37 ` [PATCH 2/3] Doc: add more detail for git-format-patch Denton Liu
2019-08-19 17:09 ` Eric Sunshine
2019-08-19 23:16 ` Denton Liu
2019-08-20 19:01 ` Junio C Hamano
2019-08-19 2:37 ` [PATCH 3/3] format-patch: infer cover letter from branch description Denton Liu
2019-08-19 17:29 ` Eric Sunshine
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
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 \
--in-reply-to=cover.1566182184.git.liu.denton@gmail.com \
--to=liu.denton@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).