I was faced with the following situation with the codebase on a Fossil
repository:
1) The codebase has a single branch, the "trunk", with a number of
check-ins (let's say 80).
2) The latest 5 check-ins, including the trunk's leaf, turned out to be a
code dead-end. I wish to make it a closed branch (let's call it "useless"),
starting from 5 check-ins ago.

Using the Web interface, I successfully managed to assign the latest 5
check-ins to the new "useless" branch and separate it from the "trunk", and
keep the 6th latest and older check-ins in the "trunk".
To this effect, on the web interface I
1) select the appropriate base check-in in the project's Timeline page;
2) click the "edit" link under the check-in's Overview section;
3) select the background color and check the option "propagate color to
descendants";
4) cancel tag "trunk", cancel special tag "branch", and check "Make this
check-in the start of a new branch" and type in name of the intended
branch, "useless".
5) Click "Apply changes". :-)

While this certainly solves my problem, I haven't managed to achieve the
same result with the command line interface. When I type
$ fossil branch new useless [checkin-id]
it creates a new branch from the indicated checkin-id, but it maintains its
descendants in the "trunk" branch.

So, is there an option to the "fossil branch new" CLI command to assign the
descentants of a certain checkin-id to the branch while also removing the
previous name of branch and tag?

Thank you in advance.
--
  João Batista
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to