On Monday, March 6, Michael Gersten wrote:
> "Greg A. Woods" wrote:
> >
> > Sounds a bit like the inverse of the vendor branch concept.
> >
> > I can't see any reason for doing this though -- beyond wanting to
> > confuse yourself and anyone else who might look at the result.
>
> How about this: After working on something, I realize that it
> needs to be checked in, but isn't really ready yet. I want to
> check it in as-is, but I didn't set up a branch before I started
> editing.
Cripes, use "cvs diff" to give you a diff of your changes, checkout
a new sandbox (or revert your old one), add the branch, apply the
diffs (using patch), commit.
> Or, how about "Ok, this is now working, lets stop using the
> current branch and go back to it's parent".
Update with the appropriate -r or -A flags? Or do you mean
"merge" your changes on the branch into another?
--Toby.
