[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110601151513.GB32270@dumpdata.com>
Date: Wed, 1 Jun 2011 11:15:13 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Jens Axboe <jaxboe@...ionio.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [git pull v3.0-rc1] What branch to base fixes for v3.0-rc1 for
block system?
On Tue, May 31, 2011 at 09:25:11PM +0200, Jens Axboe wrote:
> On 2011-05-31 21:10, Konrad Rzeszutek Wilk wrote:
> > Hey Jens,
> >
> > I've got two tiny fixes for the xen-blkback (see below):
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git for-jens/xen-blkback.fixes
> >
> > and they are based on for-2.6.40/drivers branch. Is that the way you
> > prefer to pull patches from sub-trees? Or should I rebase it on 3.0-rc1?
> > Or should send bug-fixes just directly to Linus?
>
> Once I send off the big initial merges which are in the version named
> for-2.6.40/xx branches, anything after that should just be based on my
> for-linus branch. That's what I use for post-rc1 merges with Linus.
>
> But the only real sticking point is that your branch should not contain
> something that I don't have in my for-linus. And you don't right now, so
> I just pulled it :-)
Can you repull that branch please? I've rebased it on for-linus branch
and fixed the embarrassing compilation issue it had..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists