Re: "bk pull" is not updating my local repository
Larry McVoy <[email protected]>
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Aug 23, 2004 at 04:31:59PM -0500, Timur Tabi wrote: > Thomas Glanzmann wrote: > >you just have to bk ci your deltas, not commit or propagate them. > > But if I check in the files, then I have to supply all the comments for > the changelog. What if I'm not ready to do that? > > It seems odd that I need to check in files in order to pull other files. > I've used a dozen other version control systems, and that's never been > a requirement. I've always been able to get the latest version of any > file whenever I want. Sure you can but what if you pull in updates and then you decide the updates were garbage and you want to go backwards? You no longer can because you stomped on your local changes. All BitKeeper is doing is telling you that you have local work and the new work you are trying to apply modifies the same files. If we stomped on the files or automerged them there is no way to undo that pull. It's extremely common amongst BK users to do "let's see if I want this stuff" pull. bk pull # look look look, nah, this is junk, I'll wait for it to stabilize bk unpull -- --- Larry McVoy lm at bitmover.com http://www.bitkeeper.com _______________________________________________ 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.