Hello, In my opinion, the private branch concept only works well for people working in just one computer. In the every day more common case of people developing in several computers (desktop, laptop, tablet, etc), private branches do not adapt well to the situation. Probably the solution could be the combination of two concepts that have already been discussed in the past:
1- Selective sync of some branches depending on the remote repository 2- Mark some commits as hidden and do not show them in a normal timeline RR 2013/1/3 Richard Hipp <[email protected]>: > If I understand you correctly, I believe this is what happens if you do your > lots of tiny commits into a --private branch, then merge that private branch > into trunk (or some other public branch) at the end. When you push to > another repo, on the other repo that does not contain the private branch, > the merge looks like a single commit that contains all of the changes all > mashed together into one big change _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
