On Donnerstag, 5. Juli 2007, Folker Schamel wrote:
> I think a shortcut for the repository root including "/" (e.g. "$")
> would be absolutely sufficient:
> Then use "svn cp . $tags/A", or "svn diff $tags/1.1 $tags/1.2" or whatever.
> No need for svn:layout property.
Hmmm... take it a step further, and make a "svn:shortcut" which might list "$"
as "/"? Then set "T" as "$/tags", and you can use T/1.4.0 ...
> C. Michael Pilato wrote:
> > 1. all that flexibility makes it harder for Subversion and other
> > third-party tools to recognize and treat a directory copy as a branch.
> > Common questions like, "What tags exist?" can't be answered unless the
> > answering system first understands the policy used to denote tags in a
> > given repository ("stuff immediately under /tags"; "stuff immediately
> > under an immediate subdirectory of /tags"; ...)
On Donnerstag, 5. Juli 2007, David Glasser wrote:
> ... and as an extension of this, it leads directly to the whole "no
> project-wide configuration" can of worms.
Then make a "project-wide" configuration! Simply require that the top level
directory checked out *must* include a "svn:layout" or whatever.
I believe that the additional complexity by giving a new *dimension* -- both
in code, and *in explanations* (where Branko already said that it's difficult
to grasp for users!) is not worth the "magic", esp. if you can get it in
(Whether we'd *really* get all the needed functionality, I don't know. I
didn't see a chart "What we have/What is needed" listing what is missing now,
so I can only interpolate).
> When opening the TortoiseSVN repo-browser,
> you see trunk, tags, and branches.
> When clicking the tags folder, you see all top-level tags.
> And if you really want to optimize away this single mouse click,
> then you could implement a new menu item "Open tags/ in repository
> BTW, TortoiseSVN handles /tags in a special way at some places.
> For example, when trying to commit to /tags/, you get a warning.
> Personally I like the tag/branch concept of svn very much,
> I think it is much simpler and more intuitive than the CVS mechanism.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 6 06:58:25 2007