From: Larry D'Anna <larry@elder-gods.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Wesley J. Landaker" <wjl@icecavern.net>, git@vger.kernel.org
Subject: Re: [PATCH] add new options to git format-patch: --cover-subject and --cover-blurb
Date: Fri, 5 Feb 2010 17:59:01 -0500 [thread overview]
Message-ID: <20100205225901.GA29821@cthulhu> (raw)
In-Reply-To: <7vfx5fwbws.fsf@alter.siamese.dyndns.org>
* Junio C Hamano (gitster@pobox.com) [100205 17:33]:
> The placeholder in particular and the cover letter itself in general are
> meant to be edited. I do not see much point in forcing people to edit yet
> another file and have them specify with an cover-blurb option.
>
> Not very interested.
Yes, they're meant to be edited, but if you look at the steps required to submit
a series with cover letter, it's clear it could be a bit streamlined:
1) make your branch
2) git format-patch --cover-letter
3) edit the cover letter
3) review the series, and realize you need to fix something, fix it.
4) git format-patch --cover-letter again
5) edit the cover letter, *again*. hopefully you didn't overwrite the old one.
6) git send-email --to myself
7) one last look over it in my inbox
8) git send-email --to the list
The whole thing is a lot less annoying and error-prone if you can have
git-send-email call git-format-patch.
Besides, you're not forcing anyone to edit an extra file. If you leave out
--cover-subject or --cover-blurb it just behaves in exactly the same way it
always did.
--larry
next prev parent reply other threads:[~2010-02-05 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 21:39 [PATCH] add new options to git format-patch: --cover-subject and --cover-blurb Larry D'Anna
2010-02-05 22:26 ` Wesley J. Landaker
2010-02-05 22:33 ` Junio C Hamano
2010-02-05 22:53 ` Wesley J. Landaker
2010-02-05 23:00 ` Larry D'Anna
2010-02-05 22:59 ` Larry D'Anna [this message]
2010-02-06 1:10 ` Junio C Hamano
2010-02-06 19:13 ` Jonathan Nieder
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=20100205225901.GA29821@cthulhu \
--to=larry@elder-gods.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=wjl@icecavern.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).