mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Sat, 28 Feb 2009 20:25:07 +0100	[thread overview]
Message-ID: <49A98F93.5030206@s5r6.in-berlin.de> (raw)
In-Reply-To: <20090228175218.GA4606@sirena.org.uk>

Mark Brown wrote:
[some people disregard the patch title in the Subject header]
> I believe the issue is the UI of a MUA - the subject line of a mail is
> normally presented separately to the body and isn't always as
> immediately prominent as the body so it's harder work to look at it.

That's not universally true for all MUA; and in affected MUAs only if
mails are read one-after-another, not if mails are read by looking at
the list of messages in a mailbox first, then going to the interesting
messages.  So if there are people who disregard the patch title for this
reason, then I dare to say it is because their view is limited by their
particular MUA and their individual mail reading preferences.  Their
preferences still don't make the convention go away that the Subject is
the title.  (And that the title should be a quick intro into what the
patch is about.)

> This is sensible for e-mail since the general style is that the subject
> line shouldn't be required in order to comprehend what the message is
> about

No.  The subject is the primary means to establish context for the
message (along with the mailinglist topic).  We ask people to post with
a good subject.

And since the subject already established context, there is no need to
repeat its information in the e-mail body.

> The connection with git is that it doesn't really draw a similar
> distinction so the issue isn't as immediately obvious when you're
> working within it. 

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
like quilt.  All those tools either explicitly or implicitly support the
notion that the RFC 2822 Subject header contains the patch title.  They
support it because the *people* who use those tools support it.

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.
-- 
Stefan Richter
-=====-==--= --=- ===--
http://arcgraph.de/sr/

  reply	other threads:[~2009-02-28 19:25 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 [this message]
2009-02-28 21:02               ` Mark Brown
2009-02-28 23:01                 ` Stefan Richter
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=49A98F93.5030206@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®