[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49BDADC3.6030809@kernel.org>
Date: Mon, 16 Mar 2009 10:39:15 +0900
From: Tejun Heo <tj@...nel.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC: Jens Axboe <jens.axboe@...cle.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
linux-kernel@...r.kernel.org, Russell King <rmk@....linux.org.uk>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Mike Miller <mike.miller@...com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Jeff Garzik <jgarzik@...ox.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Jeremy Fitzhardinge <jeremy@...source.com>,
Alex Dubov <oakad@...oo.com>
Subject: Re: [PATCH 11/14] block: implement and use [__]blk_end_request_all()
Hello, Bart, Jens.
Bartlomiej Zolnierkiewicz wrote:
> pata tree is based on Linus' tree _not_ on linux-next and this is very
> handy when it comes to preparing pull requests.
>
> It could be that I worry needlessly but with ~170 patches in the tree
> currently, lack of time and merge window around the corner there is
> no wonder that I'm reluctant to any experiments. However I completely
> agree that we should look into the ways of improving the process in
> the longer-term.
quilt tree is fine for leaf tree changes but problems occur when other
changes need to be based off the tree as is the case here. Is it
possible for you to provide mid-synchronization git commits? It means
starting up a new quilt tree after each synchronization point (as rc1
merge points would) but it could be an acceptable mid-point for both
trees if the number of sync points aren't too many.
Thanks.
--
tejun
--
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