linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
Date: Tue, 07 Aug 2007 16:53:32 +0200	[thread overview]
Message-ID: <46B8876C.70604@gmail.com> (raw)
In-Reply-To: <1186458941.6637.44.camel@localhost.localdomain>

On 08/07/2007 05:55 AM, James Bottomley wrote:

> I really, *really* think we need a pre-release tree that consists of all 
> the upstream targetted features (i.e. all of the for the next merge 
> window git trees) and nothing else.  -mm doesn't really satisfy this, 
> because it has so much other stuff that the people I need to get testing 
> this don't trust it.

I much agree with this. I used to run -mm at least somewhat frequently if it 
included stuff I was interested in (random features, or for example latest 
ALSA) but gave that up after I had it break on something unrelated and (to 
me) uninteresting a few times too many. There's so much in there that before 
you know it you end up spending time not on that which you wanted to spend 
time on but on something completely unrelated which given a fixed amount of 
available total time (and level/spread of knowledge/interest) gets to be a 
problem.

For latest ALSA, I now sometimes look at the ALSA repositories directly but 
otherwise it seems I'm not testing much of anything before late -rc's.

Not everything going to Linus gets there by way of -mm, but perhaps it could 
help if Andrew split off -merge from -mm, where -merge contained only stuff 
(from -mm) expected to go upstream in the next merge window.

Not sure if this is proposing that other people do more work -- wouldn't 
want do to anything of the sort...

Rene.

  parent reply	other threads:[~2007-08-07 14:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04 17:31 [GIT PATCH] scsi bug fixes for 2.6.23-rc2 James Bottomley
2007-08-07  0:51 ` Linus Torvalds
2007-08-07  3:55   ` James Bottomley
2007-08-07  4:01     ` Linus Torvalds
2007-08-07 13:12       ` James Smart
2007-08-07 16:13         ` Jeff Garzik
2007-08-07 14:31       ` James Bottomley
2007-08-07 16:20         ` Jeff Garzik
2007-08-07 16:31           ` James Bottomley
2007-08-07  7:14     ` Andrew Morton
2007-08-07 13:58       ` FUJITA Tomonori
2007-08-07 14:21         ` Jeff Garzik
2007-08-07 17:47           ` Andrew Morton
2007-08-07 14:25       ` James Bottomley
2007-08-07 14:55         ` Alan Cox
2007-08-07 14:56           ` Jeff Garzik
2007-08-07 15:11         ` Jeff Garzik
2007-08-07 15:38           ` James Bottomley
2007-08-07 15:43             ` Jeff Garzik
2007-08-07 17:51             ` Andrew Morton
2007-08-13 12:42               ` Jens Axboe
2007-08-13 15:58                 ` Jeff Garzik
2007-08-13 18:02                   ` Jens Axboe
2007-08-13 18:07                     ` Jens Axboe
2007-08-07 15:24       ` Jeff Garzik
2007-08-07 14:53     ` Rene Herman [this message]
2007-08-07 16:06     ` Jeff Garzik
2007-08-07 16:27       ` James Smart
2007-08-07 16:34         ` Jeff Garzik

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=46B8876C.70604@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).