[svnbook commit] r2694 - trunk/src/en/book

Ben Collins-Sussman sussman at red-bean.com
Sat Feb 24 18:28:15 CST 2007

On 2/24/07, C. Michael Pilato <cmpilato at red-bean.com> wrote:
> Brian W. Fitzpatrick wrote:
> > On 2/24/07, Ben Collins-Sussman <sussman at red-bean.com> wrote:
> >> No, it doesn't.  But Mike only updated the sections where we're
> >> referring to the schema in the abstract sense:  "when dealing with
> >> file:// URLs, blah blah blah..."  While this is technically correct
> >> w.r.t. the RFC, it's not consistent with what users actually type.
> >> Hence my worry.
> Yes, file:// *does* work, just as much as http:// or svn:// do.  But all
> three of them have a hostname portion which for file:// alone is allowed
> to be empty.  (It doesn't have to be, though -- you can use "localhost",
> too.)
> $  svn mkdir -m "" file://localhost/temp/repos/A
> Committed revision 1.
> $  svn mkdir -m "" file:///temp/repos/A2
> Committed revision 2.
> $
> > I agree--we have enough trouble with people typing file://path/to/foo.
> Guys, we have plenty of examples in the book that demonstrate the use of
> file:///some/path or file://localhost/some/path.  I'm only talking about
> consistifying the prose portions across the various schemas.  There are
> 16 references to "file://" and over twice as many examples of its use
> (which show "file:///...").

As a concession, can we at least explain why users sometimes see 2
slashes, and sometimes see 3 slashes?  Your explanation above is fine,
we just need to say that in the book too.

More information about the svnbook-dev mailing list