-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/05/2010 12:59 PM, Eric wrote: > On Tue, October 5, 2010 at 12:39 pm, "Laurens Van Houtven" > Actually I think there is a small issue that leaves can be closed, but not > branches, so if the only descendant of the "last" checkin in the branch is > the trunk checkin resulting from the merge, there is no way to "close" the > branch. Also nothing stops you re-using _any_ branch name later. >
I'd actually wondered about this recently as well. My project at http://hermesgps.info uses a single repository for multiple related projects, each in its own branch. I imported the repositories from Git, and there were areas in which the import generated leaves despite the presence of only one branch. I manually closed these leaves and re-tagged the commits down the line with new propagating tags, but I see several branches with the same name even though there are only a few leaves. IOW, "fossil leaves" displays correctly, but "fossil branch" displays duplicates. Not a huge thing, but trying to explain my model to contributors would be easier if I could say "each project uses a different branch" rather than "each project uses a different branch, but because my import didn't bring them in continuously, there are duplicates of some of the branches. Use leaves to get a more concise view of projects." Also, to be clear, I don't mind reusing branch names later. I just wish that branches could be closed as well, or at least that the default report skipped branches whose leaf commits were closed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyrhvsACgkQIaMjFWMehWJBAQCeKbc54ID979KfOx+X/76dqX90 q0AAniGLTOJgkEWxwBUZfyXOOf/LKDw/ =98w/ -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
