From: "Shawn O. Pearce" <spearce@spearce.org>
To: David Brown <davidb@codeaurora.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] commit: More generous accepting of RFC-2822 footer lines.
Date: Tue, 27 Oct 2009 17:05:11 -0700 [thread overview]
Message-ID: <20091028000511.GK10505@spearce.org> (raw)
In-Reply-To: <20091027234520.GA11433@quaoar.codeaurora.org>
David Brown <davidb@codeaurora.org> wrote:
> From: David Brown <davidb@quicinc.com>
>
> 'git commit -s' will insert a blank line before the Signed-off-by
> line at the end of the message, unless this last line is a
> Signed-off-by line itself. Common use has other trailing lines
> at the ends of commit text, in the style of RFC2822 headers.
>
> Be more generous in considering lines to be part of this footer.
> This may occasionally leave out the blank line for cases where
> the commit text happens to start with a word ending in a colon,
> but this results in less fixups than the extra blank lines with
> Acked-by, or other custom footers.
The nasty perl I use in Gerrit's commit-msg hook is a bit more
expressive. Basically the rule is we insert a blank line before
the new footer unless all lines in the last paragraph (so all text
after the last "\n\n" sequence) match the regex "^[a-zA-Z0-9-]+:".
> +test_expect_success 'signoff gap' '
> +
> + echo 3 >positive &&
> + git add positive &&
> + alt="Alt-RFC-822-Header: Value" &&
> + git commit -s -m "welcome
> +
> +$alt" &&
I wonder if we shouldn't also have a test case for the message:
msg="test
this is a test that
fixes: 42.
"
as the result would be expected to be:
exp="test
this is a test that
fixes: 42.
Signed-off-by A. U. Thor <...>
"
But:
msg="test
this is a test
fixes: 42
"
would produce:
exp="test
this is a test
fixes: 42
Signed-off-by A. U. Thor <...>
"
--
Shawn.
next prev parent reply other threads:[~2009-10-28 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 23:45 [PATCH] commit: More generous accepting of RFC-2822 footer lines David Brown
2009-10-28 0:05 ` Shawn O. Pearce [this message]
2009-10-28 7:14 ` Junio C Hamano
2009-10-28 14:23 ` David Brown
2009-10-28 17:13 ` David Brown
2009-10-28 18:06 ` Junio C Hamano
2009-10-28 18:17 ` David Brown
2009-11-03 16:59 ` SZEDER Gábor
2009-11-04 3:09 ` [PATCH] commit: fix too generous RFC-2822 footer handling SZEDER Gábor
2009-11-04 6:11 ` Junio C Hamano
2009-11-04 15:11 ` SZEDER Gábor
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=20091028000511.GK10505@spearce.org \
--to=spearce@spearce.org \
--cc=davidb@codeaurora.org \
--cc=git@vger.kernel.org \
/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).