Re: modifying a single file
Larry McVoy <[email protected]>
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Oct 04, 2004 at 12:37:50PM -0500, Mike Marty wrote: > I have a developer who wishes to update a single file in our parent > repository. However he doesn't want to pull changes from the parent to his > local repository. Even though there are no conflicts to this file, my > understanding is that this can't be done without cloning the parent to a > seperate local repository, right? > > However since we use BK over a shared file system, is it safe to do the > edit/commit directly on the parent? Sure, you can do that. It's considered bad form to make a habit of that because sooner or later someone will go to lunch with the file modified and someone else will have their push fail. Why doesn't he just do a clone -l locally? Note there is a very useful idiom: bk clone -lr`bk repogca` . ../clone_of_parent What that does is - calculate the greatest common ancestor of the child & parent - create a hard linked clone of the child - strips out the local only changes - leaves you with a clone of the parent The main benefit of this is when your local cpu/disk is fast and your network connection is slow, you are pushing all the hard work to the local system. -- --- 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.