Re: a minimal effort to categorize come bk commands
Wayne Scott <[email protected]> Thu, 28 Oct 2004 09:24:14 -0500 (EST)
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
From: Larry McVoy <[email protected]> > That one is dangerous and your comment isn't quite right. If you just > did a "bk new libmad-0.15.1b.tar.gz", you haven't done a commit yet, then > what you said is correct. But if that file has any committed deltas and > you do that then check will complain. More to the point this will do the same thing without as much risk. # strip all uncommitted deltas from a file: bk sfiles -pAC libmad-0.15.1b.tar.gz | bk stripdel - # strip all uncommitted deltas from ALL files: bk -R sfiles -pAC | bk stripdel - You still might delete something you didn't intend. Usually you want to just manually remove files you don't intend to commit using the discard button in citool. -Wayne _______________________________________________ Bitkeeper-users mailing list [email protected] http://bitmover.com/mailman/listinfo/bitkeeper-users To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.