From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Warn on empty commit log bodies
Date: Sun, 01 Mar 2009 00:01:38 +0100 [thread overview]
Message-ID: <49A9C252.50204@s5r6.in-berlin.de> (raw)
In-Reply-To: <20090228210223.GA23191@sirena.org.uk>
Mark Brown wrote:
> On Sat, Feb 28, 2009 at 08:25:07PM +0100, Stefan Richter wrote:
>> It isn't just a non-obvious issue with git, it is *no issue* with git in
>> the first place. It also is no issue with other patch importing tools
>
> Well, exactly. There is no issue within git so it's not obvious that
> people are going to have a problem when you're working in git.
Forget git. It's also no problem if one is never ever working "in git".
(No problems with tools anyway.)
I for one don't use git in patch creation, review, testing, submission,
and publication of patches (except for feeds to Linus and -next).
>> Since "Subject = title = beginning of changelog" is the long established
>> norm and since the other patch handling tools (and people who handle
>> patches) support this norm, checkpatch should follow this convention as
>> well and count a non-empty RFC 2822 Subject header as one non-empty
>> changelog line.
>
> As I have previously said, that is not the case in reality. There
> appears to be substantial sentiment among people handling patches that
> not having any text in the body of the e-mail makes it harder to handle
> patches.
It is indeed a problem
- if the patch title alone insufficiently describes the patch
or
- if a patch reviewer believes that it is OK to ignore patch titles.
Checkpatch cannot test for the former and should not test for the latter.
> I don't have that issue myself but I understand it and it
> seems easier to write longer changelogs than to try to change everyone's
> workflows.
So for these people your new checkpatch warning is valid.
For everybody else this warning is a false positive.
> Quite a few of the one line changelogs could probably
> benefit from being expanded a little anyway.
Granted. But only people can detect this, a script can't.
BTW, a data point:
I just looked at firewire patches post 2.6.25 and found 32 patches out
of 272 patches which only had one line as changelog line (including the
title, excluding Signed-off-by). I am still very satisfied with their
changelogs. So that would be an unnecessary checkpatch warning in 12%
of patches which I dealt with in the past few months.
However, 9 of the patches with oneliner log were for a submitted
out-of-tree driver, i.e. cleanup related. Since that cleanup is over
now, the percentage of easy to explain patches in my practice will go
down again. Therefore I will shut up now even though I still disagree
with your way of counting changelog lines. :-)
--
Stefan Richter
-=====-==--= --== ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-02-28 23:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 18:05 Mark Brown
2009-02-28 13:58 ` Stefan Richter
2009-02-28 15:58 ` Mark Brown
2009-02-28 16:14 ` Stefan Richter
2009-02-28 16:46 ` Mark Brown
2009-02-28 17:33 ` Stefan Richter
2009-02-28 17:52 ` Mark Brown
2009-02-28 19:25 ` Stefan Richter
2009-02-28 21:02 ` Mark Brown
2009-02-28 23:01 ` Stefan Richter [this message]
2009-03-01 0:18 ` Theodore Tso
2009-03-01 0:46 ` Mark Brown
2009-03-01 2:53 ` Theodore Tso
2009-03-02 13:15 ` Mark Brown
2009-03-02 15:15 ` Stefan Richter
2009-03-02 16:01 ` Mark Brown
2009-03-02 18:01 ` Andrew Morton
2009-03-02 18:24 ` Mark Brown
2009-03-02 18:34 ` Andrew Morton
2009-03-02 18:43 ` Theodore Tso
2009-03-02 19:19 ` Mark Brown
2009-03-02 19:57 ` Theodore Tso
2009-03-02 20:38 ` Mark Brown
2009-03-10 18:19 ` Andy Whitcroft
2009-02-28 17:40 ` Arjan van de Ven
2009-02-28 17:47 ` Mark Brown
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=49A9C252.50204@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=apw@canonical.com \
--cc=broonie@sirena.org.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®