Greg Stein <gstein@lyra.org> writes:
> > But that's not really the Subversion model; in
> > Subversion, the container *is* the versioned resource, and the
> > individual file or directory is just a piece of it. It makes perfect
> > sense to want to know where the versioned resource starts in that model,
> > even if the core Subversion operations don't generally need to.
>
> Hmm. Not entirely sure about this, but I can see it. For example, we talk
> about /trunk and /tags and /branches all the time. We're referring to
> particular locations *within* a repository. If the location of the
> repository isn't clear, then it is hard to talk about the relative paths
> within that repos. For example, do we talk about /svn/trunk, or /trunk? If I
> don't tell you that the repository is http://svn.collab.net/repos/svn/, then
> you can't answer the question.
How about the fact that option (2) allows users to just casually
browse a repository in their browsers? If I run 'svn info' on some
resource in my working copy, I'd much rather see a hyperlink I can
just click on, rather than some opaque repos identifier.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 1 14:34:33 2002