public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Domenico Andreoli <cavokz@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Willy Tarreau <w@1wt.eu>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Typo bug [Re: Linux 2.6.27-rc8]
Date: Thu, 2 Oct 2008 11:45:11 +0200	[thread overview]
Message-ID: <20081002094511.GA25414@tilt.dandreoli.com> (raw)
In-Reply-To: <20081002092630.GB9456@elte.hu>

On Thu, Oct 02, 2008 at 11:26:30AM +0200, Ingo Molnar wrote:
> 
> * Willy Tarreau <w@1wt.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@ono.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).

yes, asked. sorry.

> 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.

I think I got the lesson although the assymetry matter is still not that
clear to me. Anyway I also know that when you talk about code you prefer
patches to plain english so I expect you'd like others do the same ;)

Thank you,
Domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

  reply	other threads:[~2008-10-02  9:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 22:39 Linux 2.6.27-rc8 Linus Torvalds
2008-09-29 23:09 ` david
2008-09-29 23:33 ` Jiri Kosina
2008-09-30  1:56   ` Linus Torvalds
2008-09-30  1:59     ` Dave Airlie
2008-09-30  2:06       ` Arjan van de Ven
2008-09-30  2:23         ` Linus Torvalds
2008-09-30  2:24           ` Linus Torvalds
2008-09-30 12:06             ` Alan Cox
2008-09-30  3:42           ` Brandeburg, Jesse
2008-09-30 12:05           ` Alan Cox
2008-09-30  2:21       ` Linus Torvalds
2008-09-30  2:39         ` Dave Airlie
2008-09-30  3:19         ` Arjan van de Ven
2008-09-30  7:11         ` Jiri Kosina
2008-09-30  7:58           ` Eric Piel
2008-09-30 16:28             ` Luiz Fernando N. Capitulino
2008-09-30 18:27               ` Herton Ronaldo Krzesinski
2008-09-30  2:30     ` Brandeburg, Jesse
2008-09-30 22:07       ` Thomas Gleixner
2008-09-30  7:06     ` Jiri Kosina
2008-09-30 14:09       ` Krzysztof Halasa
2008-09-30 14:11         ` Jiri Kosina
2008-09-30 15:48           ` Allan, Bruce W
2008-10-01 15:37             ` Jiri Kosina
2008-09-30  7:43 ` Typo bug [Re: Linux 2.6.27-rc8] J.A. Magallón
2008-09-30  7:55   ` Ingo Molnar
2008-09-30  8:02     ` J.A. Magallón
2008-09-30  8:05       ` Ingo Molnar
2008-10-01 21:33         ` Domenico Andreoli
2008-10-02  5:27           ` Willy Tarreau
2008-10-02  9:26             ` Ingo Molnar
2008-10-02  9:45               ` Domenico Andreoli [this message]
2008-09-30 18:47     ` H. Peter Anvin
2008-09-30 19:30       ` Yinghai Lu
2008-09-30 19:59         ` H. Peter Anvin
2008-09-30 21:35           ` Yinghai Lu
2008-09-30 21:37             ` H. Peter Anvin
2008-09-30 21:42               ` Yinghai Lu
2008-09-30 22:02                 ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081002094511.GA25414@tilt.dandreoli.com \
    --to=cavokz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox