Any plans to make export work?

From: Michael Ellerman <michael@ellerman.id.au>
Date: Sep 1, 2005, 14:53 UTC
Message-ID: <200509020053.20471.michael@ellerman.id.au>

Hi Y'all,

I've been playing with export a bit, and it doesn't seem to work. Or at least it doesn't do what I think of as "work"-ing.

I'm basically doing a git-export and trying to create a quilt series out of it.

When you do a "quilt push -a" I get as far as: 06f81ea8ca09b880cadf101d7e23b500e9c164bc [PATCH] scsi: remove volatile from scsi data

which doesn't apply as it (seems to) conflict with: 152587deb8903c0edf483a5b889f975bc6bea7e0 [PATCH] fix NMI lockup with CFQ scheduler

Those two commits (and others) were merged by hand in: c46f2ffb9e7fce7208c2639790e1ade42e00b146 merge by hand (scsi_device.h)

Export gives me a patch for the merge, but it a) appears to contain everything that was merged, not just the fixup-by-hand, and b) export spits it out after both of the commits which the merge merged - which is no good as quilt doesn't even get that far.

I realise I'm trying to represent a DAG as a linear series of patches. But the merge order is a linear sequence of commits, and so it *should* be representable as a linear series of patches. I think.

Any thoughts?

cheers

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person