linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	Linus Torvalds <torvalds@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, 7 Aug 2007 10:51:44 -0700	[thread overview]
Message-ID: <20070807105144.0ba67d81.akpm@linux-foundation.org> (raw)
In-Reply-To: <1186501124.3414.32.camel@localhost.localdomain>

On Tue, 07 Aug 2007 10:38:44 -0500 James Bottomley <James.Bottomley@SteelEye.com> wrote:

> On Tue, 2007-08-07 at 11:11 -0400, Jeff Garzik wrote:
> > James Bottomley wrote:
> > > The initial bsg submit went via the block git tree ... which I believe
> > > you have in -mm.  We only started taking the updates via the scsi tree
> > 
> > Seven hours before you posted this, in 
> > <20070807001429.f8cb3b22.akpm@linux-foundation.org>, Andrew already 
> > noted it was not in -mm.
> > 
> > A trivial examination of the broken-out mm patches backs up the absence 
> >   of Jens' block tree, too.
> > 
> > So let's put this myth / bad assumption to rest, shall we?
> 
> Sorry ... I just assumed from the fact that it had been in the block git
> tree for six months that it was also in -mm.

bsg was never in the #for-akpm branch of git-block.  So I assume that
Jens had it in some other branch and for some reason never pulled it
across into #for-akpm.

It was most reasonable of you to expect that bsg had received a decent
run in -mm.

  parent reply	other threads:[~2007-08-07 17:52 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 [this message]
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
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=20070807105144.0ba67d81.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=jeff@garzik.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).