Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

[Arjan van de Ven <arjan@infradead.org>]

> > the other angle is this: if someone becomes the new maintainer, does he
> > really want to "maintain" all the really old versions of the code out
> > there that predate him, or does he only want to go forward? 
> >...
> 
> What about cases like maintainers using company email addresses and 
> changing company?
> 
> E.g. Jens is still block layer maintainer but the @suse address he used 
> for years suddenly no longer existed after he left Suse.

if you're using a current enough kernel, no big deal. If you use an old
one and it bounces, then you go look further. The biggest deal for this
feature is to find out mechanically whom to CC patches to; if you're
doing patches, you better use a recent enough kernel annyway. 
(and if you're doing patches against something ancient, you more than
likely have a modern tree somewhere for lookaside)
-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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