[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Easy comparisons between related trunks, branches, and tags

From: Marc Sherman <msherman_at_projectile.ca>
Date: 2005-11-13 14:09:54 CET

Alan Barrett wrote:
>
> It's not as general as Greg's rewrite rules. Two features that rewrite
> rules could offer that are missing from the projectroot+treeroot
> proposal are:
>
> The ability to have branches that cover only a subset of the project;

Jim's suggested a way to expand the proposal to cover this; the value of
the treeroot property is the subpath that's branched. For trees
branched from the root, it's empty.

> The ability to map from short nicknames to longer branch names (e.g.
> a rewrite rule could map from "B#foo" to "branches/gcc-foo-branch",
> while the projectroot+treeroot proposal would require the user to
> specify '+branches/gcc-foo-branch").

This, on the other hand, I explicitly didn't want to include in my
proposal. IMO, general aliasing should be the province of something
like "svn ln". If the alias is useful for "svn diff", it should be
useful for "svn co" as well, and a rewrite rule doesn't help there.

> From a syntax point of view, adding "+" as a reserved character at the
> start of a path seems less safe than adding "#" as a reserved character
> in a revision name.

Note that I was using -r +..., not --old +.... Like Jim, though, I was
definitely concentrating on the behaviour I was after, not the syntax.

- Marc

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 13 14:10:56 2005

This is an archived mail posted to the Subversion Dev mailing list.