From: Willy Tarreau <willy@w.ods.org>
To: Nauman Tahir <nauman.tahir@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] why all the patches get messed up here!!!
Date: Fri, 6 Jan 2006 18:22:47 +0100 [thread overview]
Message-ID: <20060106172247.GF7142@w.ods.org> (raw)
In-Reply-To: <f0309ff0601052340p492e4646ib8a4cde25fd29872@mail.gmail.com>
On Thu, Jan 05, 2006 at 11:40:43PM -0800, Nauman Tahir wrote:
> hi all,
> May I ask why all kernel patches just get in here in the list?
> I mean to say that isn't it better to have another list only for this
> purpose and let this mailing list be a discussion forum. I login here
> to see different issues. its a wonderful resource.
> I understand that alot of code is discussed here but in case of PATCH
> I think it would be better to have a separate archive.
> No offence just wanted to ask
Hmmm it would be terrible. Just thinking about what a conversation
would look like :
"Hi guys, I found a bug in xxx subsystem, basically it did blablabla
to my box when I tried to blablabla. I fixed it the dirty way, please
consult the patch list and look for subject XXX.
=> reply :
Hi foo,
there was an cleaner fix, yours is buggy because blablabla. please
use my reply to your mail on the patch list instead.
"
Most people here *comment* patches :
- methods
- bugs
- typos
- coding style
There's no way to do this on two separate lists. It's already very
annoying when someone posts an HTTP link to some content outside !
> Regards
> Nauman
Willy
prev parent reply other threads:[~2006-01-06 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 7:40 [RFC] why all the patches get messed up here!!! Nauman Tahir
2006-01-06 7:43 ` Arlen Christian Mart Cuss
2006-01-06 7:51 ` Nauman Tahir
2006-01-06 8:08 ` Arlen Christian Mart Cuss
2006-01-06 8:44 ` Jesper Juhl
2006-01-06 8:10 ` Coywolf Qi Hunt
2006-01-06 15:23 ` Gene Heskett
2006-01-06 17:22 ` Willy Tarreau [this message]
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=20060106172247.GF7142@w.ods.org \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nauman.tahir@gmail.com \
/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