From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11.1
Date: Sun, 06 Mar 2005 19:58:15 -0800 [thread overview]
Message-ID: <422BD157.6040304@osdl.org> (raw)
In-Reply-To: <200503062302.00040.shawn.starr@rogers.com>
Shawn Starr wrote:
> Sure, I can do this. Wrt to trivial patches, will these patches that go into
> rusty's patch bot go into Linus's tree or into the -mm tree?
>
> The reason I ask that is because a trivial patch may fix an oops if there's an
> off-by-one problem and typically I'd submit that to the trivial patch bot.
No offense intended, but Rusty's trivial bot is often too slow
for critical patches, so trivial-but-critical would be better off
going to thru the x.y tree IMO.
> That's why I was wondering about why this tree doesn't except trivial changes.
It will if they fix real problems that people are experiencing.
The trivil bot and/or kernel-janitors paths for patches are better
used for slow/non-critical patches, not patches that need quick
attention and merging.
> Thanks,
> Shawn.
>
>
> On March 6, 2005 00:06, you wrote:
>
>>On Sat, Mar 05, 2005 at 01:16:10AM -0500, Shawn Starr wrote:
>>
>>>Sounds great, I can be a QA resource for what machines I have.
>>>
>>>How do people get involved in QAing these releases?
>>
>>Get the last release and test it out. If you have problems, and have
>>simple/obvious patches, send them on.
--
~Randy
next prev parent reply other threads:[~2005-03-07 4:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 6:16 Linux 2.6.11.1 Shawn Starr
2005-03-06 5:06 ` Greg KH
2005-03-07 4:01 ` Shawn Starr
2005-03-07 3:58 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:28 Paolo
2005-03-04 19:55 ` Greg KH
2005-03-04 20:01 ` Paolo
2005-03-04 20:00 ` Jeff Garzik
2005-03-04 17:53 Greg KH
2005-03-04 17:53 ` Greg KH
2005-03-04 20:34 ` Ian Pilcher
2005-03-04 22:29 ` Greg KH
2005-03-04 20:44 ` Andrew Morton
2005-03-04 20:58 ` Greg KH
2005-03-04 21:15 ` Andrew Morton
2005-03-04 21:43 ` Greg KH
2005-03-04 21:54 ` Andrew Morton
2005-03-04 22:08 ` Greg KH
2005-03-04 21:53 ` Linus Torvalds
2005-03-04 21:59 ` Andrew Morton
2005-03-04 22:05 ` Greg KH
2005-03-04 22:36 ` Andrew Morton
2005-03-05 0:06 ` Greg KH
2005-03-05 0:28 ` Linus Torvalds
2005-03-05 7:53 ` Dave Jones
2005-03-06 5:05 ` Greg KH
2005-03-05 1:37 ` Jeff Garzik
2005-03-06 5:03 ` Greg KH
2005-03-05 9:51 ` Russell King
2005-03-05 17:19 ` Jeff Garzik
2005-03-05 17:40 ` Linus Torvalds
2005-03-05 17:46 ` Russell King
2005-03-05 21:17 ` Linus Torvalds
2005-03-05 21:49 ` Gene Heskett
2005-03-05 22:06 ` Lee Revell
2005-03-05 23:26 ` Gene Heskett
2005-03-07 17:18 ` Alan Cox
2005-03-08 20:16 ` Lee Revell
2005-03-05 17:50 ` Jeff Garzik
2005-03-05 18:22 ` Randy.Dunlap
2005-03-05 0:24 ` Jeff Garzik
2005-03-04 21:15 ` Trond Myklebust
2005-03-04 21:33 ` Jeff Garzik
2005-03-04 21:51 ` Andrew Morton
2005-03-04 21:58 ` Jeff Garzik
2005-03-05 7:11 ` James Bourne
2005-03-08 22:07 ` Bill Davidsen
2005-03-08 22:41 ` Chris Wright
2005-03-04 21:50 ` Dave Jones
2005-03-04 23:35 ` Andries Brouwer
2005-03-04 20:48 ` Steven Rostedt
2005-03-04 20:53 ` Greg KH
2005-03-04 21:02 ` Steven Rostedt
2005-03-05 18:32 ` L. A. Walsh
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=422BD157.6040304@osdl.org \
--to=rddunlap@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.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