RE: Best practices for sharing/branching?
"Dan Schreiber" <[email protected]>
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
Yes, share is the way to go, but note that if you share a folder, it is a recursively shared, and you can't unshare (or branch) just a part of it. So, you'd need to either share individual files or folders within the web site, or organize it such that the unshared parts are at a top level node that would not be shared. A "Share Branch" is just invoking the Branch command on a shared file or folder. Invoking branch on a shared item breaks the share (whereas invoking branch on an unshared item branches it to a new location in the tree). This confusing bit of terminology was brought over from VSS. The source control gods will judge whether that was wise or not :) However, you shouldn't need to "share branch" to do what you want, which is share 98% of your website to another Vault location. You may want to do a regular branch if the remaining 2% has the same filenames but will have slightly different content over time. But, it isn't necessary - you could just add those files to the new location and it would work just as well. Let me know if I've just made this more confusing. An example of your website structure might help frame the discussion if you have further questions. -Dan -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Eric Bowen Sent: Friday, December 19, 2003 8:27 PM To: [email protected] Subject: RE: [vault-list] Best practices for sharing/branching? The help file describes a "Share Branch" dialog, which sounds like the ticket, but I can't find it...