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: <20081002092630.GB9456@elte.hu>
Date:	Thu, 2 Oct 2008 11:26:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Willy Tarreau <w@....eu>
Cc:	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Typo bug [Re: Linux 2.6.27-rc8]


* Willy Tarreau <w@....eu> wrote:

> On Wed, Oct 01, 2008 at 11:33:28PM +0200, Domenico Andreoli wrote:
> > On Tue, Sep 30, 2008 at 10:05:46AM +0200, Ingo Molnar wrote:
> > > 
> > > * J.A. Magallón <jamagallon@....com> wrote:
> > > 
> > > > > heh. Could you send a patch with a changelog please?
> > > > 
> > > > Here it goes...I hope its right.
> > > 
> > > applied to tip/x86/urgent, thanks!
> > 
> > Ingo, why did you require a patch? Was not it really more simple and
> > easy for everyone to write it yourself? Since I am sure it was not only
> > a laziness matter (really?), I am very curious to know the reason.
> 
> I see two things :
>   - preserve authorship of the code
>   - "laziness" as you call it, is the only way to scale for a maintainer.

yeah, correct. Also, i asked (not required) J.A. Magallón whether he 
could send a patch - if he didnt (no time, etc.) i'd have fixed it 
myself (crediting him in the changelog).

But it's also a general principle: maintainers dont 'own' the code in 
any way and there should be no assymetry in the ability to modify the 
code. So if people are willing to fix bugs they notice, i prefer that 
far more than me doing it.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ