Greg Stein <email@example.com> writes:
> We talked at length about that. There is no need for a user to know what
> part of an HTTP URL refers to the repository and which is within. To the
> user, a URL such as http://www.lyra.org/some/path/goes/here/then/a/file.c is
> simply a versioned item.
> We've been through this before (what was it? an hour on the phone?). I'll
> keep talking if you really want to. I'd rather not, though.
Hmm. I'm not asking you guys to unmake the decision, but I think it's
worth pointing out that, while the HTTP server has complete freedom in
interpreting an http URL's path, and thus can assign it whatever
semantics it likes, a file URL is actually defined to refer to a
pre-existing structure --- a native filesystem. So it's not as clean
to split a `file:' path up that way.
And even in the case of an http URL, the user will notice that, say,
http://www.lyra.org/stuff/repo/gdb/symtab.c does support versioning
operations (because it's in a repository) while
http://www.lyra.org/stuff doesn't. I think users will always end up
asking, "So, where does the repository start?", or thinking in those
terms. So I'm not sure why it's important that the user have "no need
But see below.
> > Here's a weird situation: suppose I specify a checkout of
> > file:/usr/local/svn/foo/bar/baz/bop
> > And suppose that an svn repository (a bunch of berkeley db files)
> > lives in /usr/local/svn/. But ALSO suppose that another svn repository
> > lives in /usr/local/foo/bar/ ! Which repository should be used?
> 1) Who says we should be supporting subdirectories from an SVN repository?
> Why isn't that directory considered "owned" by SVN and offlimits to
> monkeying around?
Absolutely. The filesystem owns that directory, and will put whatever
it pleases there, under whatever name it wants. You can't put your
own stuff in there.
Received on Sat Oct 21 14:36:21 2006