2013/12/4 Andy Bradford <[email protected]>:
> Also, it would be nice if from the trunk, it was possible to mark
> something as hidden if there is also a branch tag being added. At the
> moment, if I have something that is in trunk that I want to move to the
> ``mistake'' branch and hide, I have to first move it to mistake, and
> then edit it again and add hidden.
That's a good point. I modified the ci_edit page now such
that it is possible to move a check-in to "mistake" (or any
other branch-name), Hide it and Close the branch, all in one
operation. The ci_edit page contains 3 separate checkbuttions
which control this, so you can specify exactly what you want.
I'm not sure if some more protection is needed: Any change done
through this page can just as easily been undone through
succeeding edits. For example "Branch closure" could be
hidden if the branch is "trunk", the "new branch named:" field
is not filled and "trunk" had only a single leaf.
Regarding the visible glitches, I don't think they are really
problematic for the "hidden-tag" implementation: It's a
long-standing 'bug' (IMHO) that can be created in other
ways, e.g. by shunning or when (not) syncing private
check-ins. Apparently it's not so easy to fix, as it's not
trivial when an arrow is expected to be drawn an when
not. For hiding the "mistake" branch (that's actually
what I want) no such glitches happen.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
