linux-kernel - Re: [PATCH 01/10] Fs: ext4: acl.c: fixed indent issue

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]

Date:	Sun, 26 Sep 2010 13:31:11 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Joe Perches <joe@...ches.com>
Cc:	Ted Ts'o <tytso@....edu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	T Dent <tdent48227@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/10] Fs: ext4: acl.c: fixed indent issue

Joe Perches <joe@...ches.com> writes:

> It's relatively easy to see if named
> maintainer has authored or signed a
> commit in the past few years.
>
> Perhaps you'll go through the effort to
> mark the sections as orphaned.

It wouldn't make sense to orphan code based solely on the maintainer
not committing anything in X years. Many parts of the kernel are already
finalized and need nothing from the maintainers (the only changes they
receive are things like these caused by internal kernel interface
changes). Example: ISA drivers. And I assume you look at drivers,
subsystems, directories, not mere files (many .h files weren't touched
since they were written).

You orphan the code when
a) it needs action from the maintainer, and
b) the maintainer isn't there, and
c) the above isn't going to change.
-- 
Krzysztof Halasa
--
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/