lkml.org 
[lkml]   [2020]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] MAINTAINERS add D: tag for subsystem commit prefix
From
Date
On Sat, 2020-11-28 at 08:30 -0800, Tom Rix wrote:
> On 11/28/20 8:00 AM, Joe Perches wrote:
> > On Sat, 2020-11-28 at 07:36 -0800, Tom Rix wrote:
> > > On 11/27/20 2:10 PM, Joe Perches wrote:
> > []
> > > > I think an exception mechanism would be better than a specific
> > > > mechanism added to various entries.
> > > Can you give an example of what you mean ?
> > Inherit the parent prefix then add the basename(dirname) as a default.
> >
> > For instance, changes to any subsystem of drivers/staging starts as
> > "staging: " and with "$basename(path): " appended.
>
> Ah, this is quite a bit different.
>
> As far as I can tell there is no default.

The idea is to avoid adding a D: entry to each subsystem section.

> MAINTAINERS would only have the exceptions, obviously needing drivers/foo to be 'foo:'
>
> Without the full prefix, the user would be need to use get_maintainer.pl to figure it out.

True. Or some other script.

> Are the ""'s in the D value necessary ?

Maybe not. I did that for clarity with the space after colon.
My recollection is some systems used "[subsystem]" separators
and other use / without space and not colons, but I'm for
whatever approriate changes that support standarization

I think most developer/maintainers don't care one way or
another about patch commit prefixes, but those that do care
seem to care a lot.


\
 
 \ /
  Last update: 2020-11-28 23:40    [W:0.404 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site