Branch, Separation After Share

[Tri]

Hi,

Can you please clarify some more about Share + Branch?

Scenario:

Server + Client 3.53

$/MyProject
==Code
====Config this folder is shared
==Code2
====Config this folder is shared

Operation 1: branch Code2 or Code to $/Release, the two Config folders remain shared.

Operation 2: branch any Config config folder, a dialog "Branch (Separation after Share)" pops up asking to input a comment.

I didn't get enough info from the Vault help file. Can you please provide with more explanation about the subtleties of the Share + Branch regarding the two branching operations above.

Thanks very much in advance.

[lbauer]

This is expected behavior.

Operation 1: branch Code2 or Code to $/Release, the two Config folders remain shared.

A branch in Vault has two functions -- 1) make a copy of a folder/file elsewhere in the tree -- we call this a copy-branch 2) separate a share.

Since you branched (made a copy) of Code or Code2(which were not shared folders), it didn't affect the shared subfolders.

Operation 2: branch any Config config folder, a dialog "Branch (Separation after Share)" pops up asking to input a comment.

Since you are envoking the Branch command directly on a shared item, Vault assumes you wish to separate the share. A comment box is provided so you can comment on the transaction. Note that the (copy)branch dialog also has a text box for comments on the transaction.


Let me know if you have further questions.