On 8/29/2014 09:59, Richard Hipp wrote:
No, it means that it will show the version of /path/to/file.md <http://file.md> that is on the current trunk check-in. But you just said that file doesn't exist.
I think I see what's happening. My branches have two tags on them, the one I think of as the branch tag as well as the "trunk" tag. Thus, when I check something into the branch, I am also modifying the "trunk", as far as Fossil is concerned. Fossil's "use last version with this tag" logic means it tries looking for the file on the branch, not on what I think of as the trunk.
(These branches were created in svn before the conversion to Fossil, so the odd tagging came in via the svn -> git -> fossil process.)
I think I see how to fix it, but I'd like someone clueful to bless my guess at the solution: "fossil tag cancel trunk" from a checkout of the tip of the branch.
I worry about cancelling such an important tag. It should be safe if I do this on a branch checkout, though, right?
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
