From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] checkpatch: Add ability to coalesce commit descriptions on multiple lines
Date: Tue, 20 Jan 2015 23:44:59 +0100 [thread overview]
Message-ID: <1421793899.29393.8.camel@x220> (raw)
In-Reply-To: <1421792716.2724.11.camel@perches.com>
Joe, Andrew,
On Tue, 2015-01-20 at 14:25 -0800, Joe Perches wrote:
> If a git commit description is split on consecutive lines,
> coalesce it before testing.
>
> This allows:
>
> commit <foo> ("some long
> description")
>
> Signed-off-by: Joe Perches <joe@perches.com>
> Noticed-by: Paul Bolle <pebolle@tiscali.nl>
Works as advertised (ie, that particular commit explanation doesn't
trigger an error anymore). And Andrew M. already added it to the -mm
tree.
Thanks, both of you!
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Joe Perches <joe@perches.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@canonical.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hsselbarth@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Valentin Rothberg <valentinrothberg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Add ability to coalesce commit descriptions on multiple lines
Date: Tue, 20 Jan 2015 23:44:59 +0100 [thread overview]
Message-ID: <1421793899.29393.8.camel@x220> (raw)
In-Reply-To: <1421792716.2724.11.camel@perches.com>
Joe, Andrew,
On Tue, 2015-01-20 at 14:25 -0800, Joe Perches wrote:
> If a git commit description is split on consecutive lines,
> coalesce it before testing.
>
> This allows:
>
> commit <foo> ("some long
> description")
>
> Signed-off-by: Joe Perches <joe@perches.com>
> Noticed-by: Paul Bolle <pebolle@tiscali.nl>
Works as advertised (ie, that particular commit explanation doesn't
trigger an error anymore). And Andrew M. already added it to the -mm
tree.
Thanks, both of you!
Paul Bolle
next prev parent reply other threads:[~2015-01-20 22:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 9:32 [PATCH v4] ARM: mvebu: remove two selects of ARM_ERRATA_753970 Paul Bolle
2015-01-19 9:32 ` Paul Bolle
2015-01-19 9:38 ` Paul Bolle
2015-01-19 9:38 ` Paul Bolle
2015-01-20 22:25 ` [PATCH] checkpatch: Add ability to coalesce commit descriptions on multiple lines Joe Perches
2015-01-20 22:25 ` Joe Perches
2015-01-20 22:44 ` Paul Bolle [this message]
2015-01-20 22:44 ` Paul Bolle
2015-01-19 11:39 ` [PATCH v4] ARM: mvebu: remove two selects of ARM_ERRATA_753970 Russell King - ARM Linux
2015-01-19 11:39 ` Russell King - ARM Linux
2015-01-21 10:42 ` Gregory CLEMENT
2015-01-21 10:42 ` Gregory CLEMENT
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=1421793899.29393.8.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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 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.