linux-kernel - Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch

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: <20070813071606.GF21089@ftp.linux.org.uk>
Date:	Mon, 13 Aug 2007 08:16:06 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Joe Perches <joe@...ches.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

On Sun, Aug 12, 2007 at 10:49:34PM -0700, Joe Perches wrote:
> I grew weary of looking up the appropriate
> maintainer email address(es) to CC: for a patch.

Does the acronym GAFL ring any bells?  It's not that idea is worthless -
it sure as hell is a useful thing, but what the bleeding hell is that
splitup supposed to achieve?

Please, people, try to think for a minute.  Patch series are good not
just because; there are rational reasons for that.  None of those
applies here; if anything, you've made sure that this patchbomb will
be less reviewed.

Seriously, get a fucking life.  This is way past ridiculous.  It does not
make changes easier to test.  It does not help bisect.  It does not help
to make changes more self-contained.  It does not reduce the odds of
conflict with pending patches.  It does not simplify conflict resolution
when porting.  It does not split the change into easier understood parts.
Hell, it doesn't even make it easier to revert broken parts.

Use the common sense, folks.  Please.
-
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/