linux-kernel - Re: rfc: rewrite commit subject line for subsystem maintainer preference tool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1011170150060.7420@pobox.suse.cz>
Date:	Wed, 17 Nov 2010 01:53:35 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Randy Dunlap <rdunlap@...otime.net>,
	Florian Mickler <florian@...kler.org>,
	Joe Perches <joe@...ches.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: rfc: rewrite commit subject line for subsystem maintainer
 preference tool

On Wed, 17 Nov 2010, Stefan Richter wrote:

> > > I don't know what you asked Joe to change, but asking someone to use
> > > the documented canonical patch format:
> > 
> > > <quote>
> > > The canonical patch subject line is:
> > 
> > >     Subject: [PATCH 001/123] subsystem: summary phrase
> > > </quote>
> > 
> > > should be fine.  And there is no need for printf-ish templates
> > > for this in MAINTAINERS either.
> > 
> > That's exactly what I asked him to do.  He said he's not willing to use
> > anything for "subsystem" which can't be automatically generated.
> 
> Why should we codify our conventions in MAINTAINERS to accommodate the
> specific problem of virtually a _single_ patch author?
> 
> Conventions are living and are being adjusted all the time, as code
> organization changes, people join and go, projects start and cease.
> 
> Said author please looks the conventions up in the git history.  If he
> finds that this decelerates his patch generation rate, he can surely
> code a script that looks into git for him and suggests plausible
> prefixes for his patch titles to him.  Or he can collect a kind of
> database (a config file) locally for his own use in which he records
> conventional prefixes on the go.

Come on guys, this debate is really horribly boring.

Either the maintainer wants the patch. Then he is certainly able to apply 
it no matter the subject line (I personally am getting a lot of patches 
which don't follow the format I am using in my tree ... converting 
Subject: lines is so trivial that I have never felt like bothering anyone 
about it ... it's basically single condition in a shellscript). Or the 
maintainer doesn't feel like the patch is worth it, and then the 
subject-line format really doesn't matter.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/