Hiho, Yesterday i did an odd thing and i'm curious about whether the result is correct:
a) want to commit to avoid code loss but found a bad bug in last-minute testing, so create a branch: f commit --branch no-value ... b) ...fix bug... it wasn't as bad as i thought... f commit --branch trunk So now i'm back on the trunk. It can be seen here: http://fossil.wanderinghorse.net/repos/cwal/index.cgi/timeline?c=2013-05-31 i didn't notice immediately, but i now see that the trunk i originally branched from is still opened, leading to two open leaves on the trunk: http://fossil.wanderinghorse.net/repos/cwal/index.cgi/leaves Of course i can close the older one, but before i do, i wanted to ask if this is the expected behaviour, or if the older one should automatically be closed when that same branch is committed to down the line? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
