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
Regards
Nauman
Hi,
This list is also for discussing the patches and their effects, so other
developers can see them clearly and take a look!
- Arlen.
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
>
>Regards
>Nauman
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
On 1/5/06, Arlen Christian Mart Cuss <[email protected]> wrote:
> Hi,
>
> This list is also for discussing the patches and their effects, so other
> developers can see them clearly and take a look!
>
> - Arlen.
>
You are right Arlen but what irritates me is when I login here there
is a long list of PATCHES and i have to move all those without reading
them because I no its going to address very specific issue. I still
think Patches should be moved to some other archive.
I may have been selfish here :) .
kindly dont TOP POST
Nauman
> 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
> >
> >Regards
> >Nauman
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to [email protected]
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
> >
> >
> >
>
>
Nauman Tahir wrote:
>On 1/5/06, Arlen Christian Mart Cuss <[email protected]> wrote:
>
>
>>Hi,
>>
>>This list is also for discussing the patches and their effects, so other
>>developers can see them clearly and take a look!
>>
>> - Arlen.
>>
>>
>>
>You are right Arlen but what irritates me is when I login here there
>is a long list of PATCHES and i have to move all those without reading
>them because I no its going to address very specific issue. I still
>think Patches should be moved to some other archive.
> I may have been selfish here :) .
>kindly dont TOP POST
>Nauman
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
You use GMail, right? Beside the `Search the Web' button at the top of
your Inbox, you should see a small link: `Create a filter'. Click it.
In the `Subject' box, write `[patch]'. You can then click `Next step'.
You can move it to a different folder, star it, apply a label, delete
it, etc.
Then, repeat for `[patch', to catch things like `[patch 0/12]', and so on.
Hope this helps,
Arlen.
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
A discussion forum on what topic then? Don't you see that we can only
use patch to accurately express ourselves?
> 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
The most weird thought I hear this year, no offence really.
--
Coywolf Qi Hunt
On 1/6/06, Nauman Tahir <[email protected]> wrote:
> On 1/5/06, Arlen Christian Mart Cuss <[email protected]> wrote:
> > Hi,
> >
> > This list is also for discussing the patches and their effects, so other
> > developers can see them clearly and take a look!
> >
> > - Arlen.
> >
> You are right Arlen but what irritates me is when I login here there
> is a long list of PATCHES and i have to move all those without reading
> them because I no its going to address very specific issue. I still
Well, some of us do read those patches, or at least a subset of them.
Also, often a patch posted to the list serves as a startingpoint for
discussion.
> think Patches should be moved to some other archive.
I disagree. If you don't want to see the patches, then filter them out
at your end, there's a nice solution :)
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
On Friday 06 January 2006 03:10, Coywolf Qi Hunt wrote:
[...]
>The most weird thought I hear this year, no offence really.
Yes, but the year is quite young yet, CQH. Surely there will be
something even more off the wall by Dec 31st. I believe there is a
Murphy's Law corrollary about that but cannot quote it from memory,
that being the second thing to go you know. Perhaps someone can
refresh our memories?
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
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