On Fri, May 29, 2015 at 6:29 PM, <to...@acm.org> wrote: > As to what happened you probably guessed right. I must have used the > --branch option from within the 'mistake' branch. I was (until just now) > under the impression that the --branch option either starts a new branch > (if the name given is not already a branch), or commits against that branch > if it already exists. What I now understand (from what happened, and your > explanation) is that --branch simply creates a new branch with whatever > name you give it (even if it already exists), without warning that this > will cause a (most likely) unintended 'fork'. Again, something that may > need revising, perhaps with the addition of a warning.
I suspect, in most case, multiple independent branches with the same name are not a problem. But trunk is a special case that may warrant a warning. (I'm pretty my team doesn't have duplicate branch names because our policy requires us to include either a Requirement Number, a Change Request Number or Release ID as part of branch names.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
