All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@m1k.net>
To: "Radoslaw \"AstralStorm\" Szkodzinski" <astralstorm@gorzow.mm.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MM kernels - how to keep on the bleeding edge?
Date: Tue, 26 Jul 2005 16:26:03 -0400	[thread overview]
Message-ID: <42E69C5B.80109@m1k.net> (raw)
In-Reply-To: <20050726221506.416e6e76.astralstorm@gorzow.mm.pl>

Radoslaw AstralStorm Szkodzinski wrote:

>On Tue, 26 Jul 2005 15:45:41 -0400
>Michael Krufky <mkrufky@m1k.net> wrote:
>
>> have filters set up so that my mailer puts all mm-commits messages 
>>from the mailing list into a special "mm-commits" folder.  Each time 
>>Andrew releases an -mm kernel, I rename my "mm-commits" folder to 
>>"mm-commits-%version%", such as "mm-commits-2.6.13-rc3-mm2"  (I will 
>>probably have to create a folder like this tomorrow, or in a few 
>>hours/days ;-) ... Then I create a new "mm-commits" folder to hold all 
>>new patches not yet in the latest -mm kernel.  As of right now, my 
>>current "mm-commits" mail folder has 153 patches in it, although I think 
>>I may have lost a patch or two...
>>    
>>
>The problem is detecting if or when the latest -mm got created.
>If I have to do it by hand, it becomes a major PITA.
>I could use RSS to do this, but some patches may still hit the wrong
>folder. What's more it would create unnecessary network load.
>There are sometimes only a few minutes between "patch in -mm1"
>and "patch in -mm2".
>
There's an RSS feed for -mm ??? Where is that located?

-- 
Michael Krufky



  reply	other threads:[~2005-07-26 20:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 16:58 MM kernels - how to keep on the bleeding edge? Radoslaw AstralStorm Szkodzinski
2005-07-26 19:45 ` Michael Krufky
2005-07-26 20:15   ` Radoslaw AstralStorm Szkodzinski
2005-07-26 20:26     ` Michael Krufky [this message]
2005-07-26 21:41       ` Andrew Morton
2005-07-26 22:32         ` Andrew Morton
2005-07-26 22:52           ` Radoslaw AstralStorm Szkodzinski
2005-07-26 22:49         ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:11           ` Andrew Morton
2005-07-26 23:25             ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:35               ` Andrew Morton
2005-07-26 23:54                 ` Randy Dunlap
2005-07-27  0:00                 ` Radoslaw AstralStorm Szkodzinski
2005-07-27  0:08                   ` Andrew Morton
2005-07-30  2:39             ` Paul Jackson
2005-07-27  0:40         ` Michael Krufky
2005-07-27  1:02           ` Michael Krufky
2005-07-27  1:04           ` Andrew Morton
2005-07-27  1:13             ` Michael Krufky

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=42E69C5B.80109@m1k.net \
    --to=mkrufky@m1k.net \
    --cc=astralstorm@gorzow.mm.pl \
    --cc=linux-kernel@vger.kernel.org \
    /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.