[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.01.1301302303180.11666@nerf07.vanv.qr>
Date: Wed, 30 Jan 2013 23:16:31 +0100 (CET)
From: Jan Engelhardt <jengelh@...i.de>
To: Tom St Denis <tstdenis@...iptictech.com>
cc: Alexander Holler <holler@...oftware.de>,
Borislav Petkov <bp@...en8.de>,
Eric Dumazet <erdnetdev@...il.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
David Miller <davem@...emloft.net>,
steffen klassert <steffen.klassert@...unet.com>,
herbert@...dor.apana.org.au, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Michal Kubecek <mkubecek@...e.cz>,
Mike Galbraith <bitbucket@...ine.de>
Subject: Re: IPsec AH use of ahash
On Sunday 2013-01-20 14:54, Tom St Denis wrote:
>>
>> > You should really try running checkpatch.pl over code that's
>> > already in the kernel before you call out new contributors on it.
>> >
>> > How is this supposed to not be adversarial when I can't even use
>> > the Kernel source itself as a reference?
>>
>> In case of the kernel the chicken and egg problem can be answered
>> without any questions, most source existed before checkpatch.pl
>> (evolved
>> to the current state).
>
>We clearly have different interpretations of the word "maintainer"
>then... If they're not maintaining the code then are they really the
>maintainers of it?
Maintainers maintain code. From own experience - I too have some
projects that are *only* "maintained" - that includes maintaining the
status quo, keeping it compiling and taking patches that require no
more than 5 minutes to think about.
To support users, especially ones with fire-and-forget submissions,
an "integrator" (for the lack of a better word for cleaning guy)
or "developer" to take up their posting is required.
But it often lacks one or more.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists