> Right. A branch (even a private branch) lives in a repository. If > you do two or more check-outs from the same local repository, all > the changes see the same set of branches. If you want one > check-out to not see some branches, then clone the repository and > do checkouts from different clones.
Agree. > Fossil opens the most recent check-in. If you want to open the > most recent check-in from the branch named "trunk" then do: > > fossil open ../local.fossil trunk > > You can, of course, replace "trunk" in the example above with any > other branch name, or tag name, or SHA1-hash prefix that you want. Thanks. This is workable. However, IMHO, in absence of explicit branch name, it is more intuitive to open from "trunk" branch rather than take latest one, which may be from a private or public branch. It removes uncertinity to some extent. > > 1. If I have two private branches with same name, how can I > > differentiate between them? > > Well, you could do "fossil ui" and browse around to see which > check- ins are which. You might want to relabel on of the > "branches" to something different to help you distinguish them in > the future. With more than one private branches with same name, if I do "fossil open local.fossil private", I assume it will open most recent private branch? > Yes. The --private option makes sure that the branch is private. > The --branch option simply changes its name. You can also use > --bgcolor to change the default background color to something > other than orange. That's great! - Altu -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com! _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
