Re: state of the 2.6.13 transition

On Tue, 2005-09-20 at 21:55 +0100, Ian Molton wrote:
> I've patched a lot of stuff but havent comitted it because I cant test 
> it. it seems that HEAD is "missing" some files needed to build and I 
> dont understand why.
> 
> If anyone could explain it, I'd love to know the reason...

>From what I gather, the reason that the HEAD is broken is that 2.6.13
has been imported onto the vendor branch but not yet fully merged into
the trunk.  This is just the way that vendor branches in CVS work: it is
a bit unfortunate, but you have to live with it.  Essentially, between
the time that you do "cvs import" and the time that you commit the final
merge result, the tree will be in an inconsistent state and most likely
broken.  To minimize disruption, you need to either (a) keep that time
as short as possible, or (b) do the merge entirely in a working tree,
without importing onto a vendor branch at all, in which case the HEAD is
not affected at all until you commit the changes.

Why are you not able to test the code that you've patched?

p.