All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arlen Christian Mart Cuss <celtic@sairyx.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, 06 Jan 2006 19:08:01 +1100	[thread overview]
Message-ID: <43BE2561.3040404@sairyx.org> (raw)
In-Reply-To: <f0309ff0601052351s240c8e3bwb5ab5c4deb852314@mail.gmail.com>

Nauman Tahir wrote:

>On 1/5/06, Arlen Christian Mart Cuss <celtic@sairyx.org> 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 majordomo@vger.kernel.org
>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.


  reply	other threads:[~2006-01-06  8:07 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 [this message]
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

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=43BE2561.3040404@sairyx.org \
    --to=celtic@sairyx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.