cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@hansenpartnership.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC] MAINTAINERS tag for cleanup robot
Date: Sat, 21 Nov 2020 09:18:57 -0800	[thread overview]
Message-ID: <5843ef910b0e86c00d9c0143dec20f93823b016b.camel@HansenPartnership.com> (raw)
In-Reply-To: <20201121165058.1644182-1-trix@redhat.com>

On Sat, 2020-11-21 at 08:50 -0800, trix at redhat.com wrote:
> A difficult part of automating commits is composing the subsystem
> preamble in the commit log.  For the ongoing effort of a fixer
> producing
> one or two fixes a release the use of 'treewide:' does not seem
> appropriate.
> 
> It would be better if the normal prefix was used.  Unfortunately
> normal is
> not consistent across the tree.
> 
> 
> 	D: Commit subsystem prefix
> 
> ex/ for FPGA DFL DRIVERS
> 
> 	D: fpga: dfl:
> 

I've got to bet this is going to cause more issues than it solves. 
SCSI uses scsi: <driver>: for drivers but not every driver has a
MAINTAINERS entry.  We use either scsi: or scsi: core: for mid layer
things, but we're not consistent.  Block uses blk-<something>: for all
of it's stuff but almost no <somtehing>s have a MAINTAINERS entry.  So
the next thing you're going to cause is an explosion of suggested
MAINTAINERs entries.

Has anyone actually complained about treewide:?

James




  parent reply	other threads:[~2020-11-21 17:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 16:50 [Cluster-devel] [RFC] MAINTAINERS tag for cleanup robot trix
2020-11-21 17:10 ` Joe Perches
2020-11-22 16:33   ` Tom Rix
2020-11-22 18:22     ` Joe Perches
2020-11-23 17:06       ` Tom Rix
2020-11-21 17:18 ` James Bottomley [this message]
2020-11-21 18:02   ` Joe Perches
2020-11-23 15:52   ` Jani Nikula
2020-11-23 16:17     ` Lukas Bulwahn
2020-11-22  3:23 ` Matthew Wilcox
2020-11-22 14:46   ` Tom Rix
2020-11-22 14:56     ` Matthew Wilcox
2020-11-22 16:10       ` Tom Rix
2020-11-22 16:49         ` James Bottomley
2020-11-22 18:23           ` Joe Perches
2020-11-22 22:33             ` Finn Thain
2020-11-23  0:53               ` Joe Perches

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=5843ef910b0e86c00d9c0143dec20f93823b016b.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.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;
as well as URLs for NNTP newsgroup(s).