[PATCH] format-patch: Generate a newline between the subject header and the message body.

DORMANTno replies

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

[PATCH] format-patch: Generate a newline between the subject header and the message body.

From: Robert Shearman <hidden>
Date: 2016-06-15 22:42:33

format-patch previously didn't generate a newline after a subject. This 
caused the diffstat to not be displayed in messages without a blank line 
and the first blank line to be eaten in messages with a blank line.

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.
---
  commit.c |   14 ++++++++++++--
  1 files changed, 12 insertions(+), 2 deletions(-)

Re: [PATCH] format-patch: Generate a newline between the subject header and the message body.

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:42:33

Robert Shearman wrote:
format-patch previously didn't generate a newline after a subject. This 
caused the diffstat to not be displayed in messages without a blank line 
and the first blank line to be eaten in messages with a blank line.
Does this _enforce_ separating commit message into subject+empty
line+description? What about commit messages without this structire (e.g.
legacy commit messages from import from other SCM, e.g. GNU ChangeLog
style)?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

Re: [PATCH] format-patch: Generate a newline between the subject header and the message body.

From: Robert Shearman <hidden>
Date: 2016-06-15 22:42:33

Jakub Narebski wrote:
Robert Shearman wrote:
 
quoted
format-patch previously didn't generate a newline after a subject. This 
caused the diffstat to not be displayed in messages without a blank line 
and the first blank line to be eaten in messages with a blank line.
   
Does this _enforce_ separating commit message into subject+empty
line+description? What about commit messages without this structire (e.g.
legacy commit messages from import from other SCM, e.g. GNU ChangeLog
style)?
It only affects commits exported into email style. It has nothing to do
with the structure of GIT commit messages or those of any other SCM.

-- 
Rob Shearman
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help