From: Robert Shearman <rob@codeweavers.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] format-patch: Generate a newline between the subject header and the message body.
Date: Thu, 13 Jul 2006 22:55:30 +0100 [thread overview]
Message-ID: <44B6C152.8000204@codeweavers.com> (raw)
In-Reply-To: <7v7j2huqfj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>Junio C Hamano <junkio@cox.net> writes:
>
>
>
>>Robert Shearman <rob@codeweavers.com> writes:
>>
>>
>>
>>>This patch inserts a newline in two places - once in the loop to
>>>separate the subject part of the commit message from the body part of
>>>the commit message and another after the loop to counteract the eating
>>>of whitespace at the end of the message.
>>>
>>>
>>Thanks.
>>
>> * Please sign your patch.
>>
>> * This breaks a handful t4013 tests, but all in a good way (in
>> other words, the expected output files were wrong).
>>
>>I'll fix up the t/t4013/diff.* files myself.
>>
>>
>
>Actually, I take that back. This breaks normal commit log
>messages by adding extra blank lines. The extra LF is needed
>when the commit log does not have any message (just title).
>
>
Ok, I'll resend with that fixed.
>I'll be tweaking a few tests in t4013 to catch future breakage
>of this kind.
>
Thanks.
--
Rob Shearman
next prev parent reply other threads:[~2006-07-13 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 12:03 [PATCH] format-patch: Generate a newline between the subject header and the message body Robert Shearman
2006-07-13 19:38 ` Jakub Narebski
2006-07-13 20:03 ` Robert Shearman
2006-07-13 21:31 ` Junio C Hamano
2006-07-13 21:48 ` Junio C Hamano
2006-07-13 21:55 ` Robert Shearman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 22:17 Robert Shearman
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=44B6C152.8000204@codeweavers.com \
--to=rob@codeweavers.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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.