mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Joe Perches <joe@perches.com>, kernel-janitors@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Andy Whitcroft <apw@canonical.com>,
	Matteo Croce <mcroce@redhat.com>,
	Wang YanQing <udknight@gmail.com>
Subject: Re: [v3] checkpatch: add dedicated checker for 'Fixes:' tag
Date: Wed, 29 Apr 2020 08:45:11 +0200	[thread overview]
Message-ID: <dec3d317-8381-a4d9-efb9-0418f9b42a55@web.de> (raw)
In-Reply-To: <a2d7dbae193800ce430321d3fcc71ab5d1a5ed03.camel@perches.com>

> btw:  I suggested this patch last year.
>
> https://lore.kernel.org/lkml/40bfc40958fca6e2cc9b86101153aa0715fac4f7.camel@perches.com/

Thanks for this link to the previous discussion topic “linux-next:
Fixes tag needs some work in the tip tree”.
https://lkml.org/lkml/2019/1/17/966

With which script did you determine the presented statistic for variations
in the usage of details for such tags?

Will another update become interesting how often shorter commit identifiers
are still published for Linux patches?

Regards,
Markus

      reply	other threads:[~2020-04-29  6:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  2:02 [PATCH v3] " Wang YanQing
2020-04-28  6:21 ` Markus Elfring
2020-04-28 14:06   ` Wang YanQing
2020-04-28 14:54     ` [v3] " Markus Elfring
2020-04-28 10:52 ` [PATCH v3] " Markus Elfring
2020-04-28 16:18   ` Wang YanQing
2020-04-29 15:18     ` [v3] " Markus Elfring
2020-04-28 16:10 ` [PATCH v3] " Joe Perches
2020-04-28 23:17   ` Joe Perches
2020-04-29  6:45     ` Markus Elfring [this message]

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=dec3d317-8381-a4d9-efb9-0418f9b42a55@web.de \
    --to=markus.elfring@web.de \
    --cc=alexei.starovoitov@gmail.com \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcroce@redhat.com \
    --cc=udknight@gmail.com \
    /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®