From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: Eric Kidd <git@randomhacks.net>, git@vger.kernel.org
Subject: Re: [PATCH v2] filter-branch: Add more error-handling
Date: Wed, 11 Feb 2009 14:28:04 -0800 [thread overview]
Message-ID: <7v8wocbocr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090212063038.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Thu, 12 Feb 2009 06:30:38 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> Quoting Junio C Hamano <gitster@pobox.com>:
>
>> This goes after three-dashes; people who read "git log" output wouldn't
>> know nor care what was in v1.
>>
>> Subject: Fix X under condition Z
>>
>> X should do Y if condition Z holds, but it does not. This can result
>> in broken results such as W and V.
>>
>> This patch fixes X by changing A, B and C.
>>
>> Thanks for M, N and O for reviewing and suggesting improvements.
>>
>> Signed-off-by: A U Thor <au.thor@example.xz>
>
> I think you meant this as a sample to follow. Can we add it to Documentation/SubmittingPatches?
I did mean it as such, but I doubt it is good enough to be in in the
document (primarily because I wrote it).
Just quoting the above verbatim does not make it clear that "Thanks for M,
N..." is usually not even wanted, but was merely a suggestion for this
specific case of Eric's commit, iow, _only if he wanted to_. We need more
commentary like that, but with too much details, it would cease to be a
generic recommendation.
Also, the above is not suitable for new features at all as a template.
prev parent reply other threads:[~2009-02-11 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 14:09 [PATCH] git-filter-branch: Add more error-handling Eric Kidd
2009-02-11 14:58 ` Johannes Sixt
2009-02-11 15:36 ` Johannes Sixt
2009-02-11 15:24 ` Johannes Schindelin
2009-02-11 17:15 ` [PATCH v2] filter-branch: " Eric Kidd
2009-02-11 19:03 ` Junio C Hamano
2009-02-11 19:34 ` Eric Kidd
2009-02-11 20:03 ` [PATCHv3] " Eric Kidd
2009-02-11 20:48 ` Johannes Schindelin
2009-02-11 21:00 ` Eric Kidd
2009-02-11 21:10 ` [PATCHv4] " Eric Kidd
2009-02-11 21:30 ` [PATCH v2] " Nanako Shiraishi
2009-02-11 22:28 ` Junio C Hamano [this message]
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=7v8wocbocr.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@randomhacks.net \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.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.
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).