Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> In the documentation it has been stated that one should give tag > before making a branch since there may be need to check out files ar > that status. Yes, that's generally a good idea- Some kind of new syntax to refer to the base of a branch without requiring a separate tag might be a nice addition, though. Or is there maybe something like this already? > Now my question that which of the following should be practiced and > why? > > 1) Before creating a branch one should give a tag to the file and > then create a branch. And then continue making changed in both the > main trunk as well as the branch That's pretty much it yes. > 2) One should make a branch first. Then he should give one tag each > to branch as well the main trunk and then only continue to make > changes in the main trunk as well as the branch Several things to note: - You couldn't assign the same tag to different revisions (i.e. one on the trunk and one on a branch) - Tags and branches are applied to revisions, not branches, thus, unless you have already committed changes on the branch, tagging the branch right after having created it will put the tag on the trunk revision that the branch stems from - there simply isn't anything else to apply it to. Hope this helps. -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)