"Hans-Emil Skogh" <Hans-Emil.Skogh@tritech.se> wrote:
> How do you detect what is a tag?
A copy-from-path with no further *node* (with the respective options
activated. there may be modifications that do not show up), no further
copies have been created from it and its path contains the element
"tags". Other path might be tags as well but thier structure may be
of interest to the user.
> I'd propose to change that definition to "a copy-from-path that has
> no modification but may be deleted".
For the tags folding feature, I will go even further:
* A path that contains an element matching any of the configurable
tags patterns is considered a tag. (currently: "tags", future: also
user-defined patterns like "* - QA?")
* Tags will not be folded, if they have been modified. A specific
"ignore tag modifications" is allow those to be folded, instead.
* Deleted tags will be folded. They show up in the tooltip as
* Renamed tags will be folded. They show up as "alias $tagName"
* Tags that got copied can be folded as well (according to the
rules above), if "exact copy source" is not active. The copy
will then be attached to the node that the tag was made from.
* Tags may be folded recursively, if the "hide non-modifying
branches" is active (this feature is yet to be implemented).
- revgraph for some file /trunk/foo.txt
- /trunk got tagged as /tags/1.0
- /tags/1.0 was copied to /branches/hotfix
- /branches/hotfix got tagged as /tags/1.0.1
- foo.txt has not been modifed
In that case /tags/1.0 and /tags/1.0.1 will show up as folded
tags in the tooltip at the last previous modification node of
/trunk/foo.txt. The branch will not show up.
Received on Thu Jul 12 14:52:32 2007