[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b579153b-3f6d-722c-aea8-abc0d026fa0d@infradead.org>
Date: Fri, 13 Sep 2019 08:00:42 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Dan Carpenter <dan.carpenter@...cle.com>,
Jonathan Corbet <corbet@....net>
Cc: Dave Jiang <dave.jiang@...el.com>,
ksummit-discuss@...ts.linuxfoundation.org,
linux-nvdimm@...ts.01.org, Vishal Verma <vishal.l.verma@...el.com>,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS:
Maintainer Entry Profile
On 9/13/19 4:48 AM, Dan Carpenter wrote:
>> So I'm expecting to take this kind of stuff into Documentation/. My own
>> personal hope is that it can maybe serve to shame some of these "local
>> quirks" out of existence. The evidence from this brief discussion suggests
>> that this might indeed happen.
>
> I don't think it's shaming, I think it's validating. Everyone just
> insists that since it's written in the Book of Rules then it's our fault
> for not reading it. It's like those EULA things where there is more
> text than anyone can physically read in a life time.
Yes, agreed.
> And the documentation doesn't help. For example, I knew people's rules
> about capitalizing the subject but I'd just forget. I say that if you
> can't be bothered to add it to checkpatch then it means you don't really
> care that strongly.
If a subsystem requires a certain spelling/capitalization in patch email
subjects, it should be added to MAINTAINERS IMO. E.g.,
E: NuBus
--
~Randy
Powered by blists - more mailing lists