From: "H. Peter Anvin" <hpa@zytor.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: the right time to run my super-duper, kernel cleanup scripts?
Date: Sat, 13 Jun 2009 10:49:37 -0700 [thread overview]
Message-ID: <4A33E6B1.1040203@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0906130907070.4074@localhost>
Robert P. J. Day wrote:
> i figure it's almost time to annoy the crap out of everyone again by
> running my standard source "cleanup" scripts to track down things
> like, well, this:
>
> http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup
>
> i'm thinking that the right time is after the chaos of the merge
> window is mostly over so ... once rc1 is out? is that about the right
> time to give any fixes a chance to settle?
>
Yes, run that stuff on -rc1 and then notify people to fix it.
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2009-06-13 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 13:10 the right time to run my super-duper, kernel cleanup scripts? Robert P. J. Day
2009-06-13 17:49 ` H. Peter Anvin [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=4A33E6B1.1040203@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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