VCS labelling rule for branches

Is there a shorthand for this kind of labelling rule?  


trunk=>tags
branches/1.1=>tags
branches/1.2=>tags
branches/1.3=>tags
branches/1.4=>tags
branches/1.5=>tags
branches/1.6=>tags

I suppose I can eventually start discarding old branches, but even with only 8 VCS Roots serving 16 building configurations, it's a bit of a handful to manage.
1 comment
Comment actions Permalink

Hello Richard,

So far there is no way to simplify this, please vote for the corresponding issue: TW-6183.

0

Please sign in to leave a comment.