Hello, James.
James Bottomley wrote:
> On Wed, 2009-05-13 at 18:21 +0900, Tejun Heo wrote:
>>> I have reverted commit b1f744937f1be3e6d3009382a755679133cf782d
>>> ("block: move completion related functions back to blk-core.c") and
>>> applied the following patch (which I realise is probably not
>>> correct) for today. Maybe someone can come up with a better
>>> solution for the scsi guys and me.
>> Hmmm... is there a SCSI tree which won't be rebased? Then I can pull
>> blk tree into it and SCSI tree can go on from that point on.
>
> Not really ... especially now there's a proposal to redo the mvsas
> patch. However, block can run a postmerge tree with the changes in
> them.
Aieee... Yeah, I guess I can maintain temporary merge tip for blk and
scsi (that's what you're talking about, right?). Out of curiousity,
is there any reason not to use more standard git workflow? Developers
(kernel devs at least) are now pretty comfortable with git and trees
merging and splitting off. I can't really see much value in rebasing
these days.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
