Re: Older versions through http-repository browsing

> I'd much rather just let 'svn info' reveal the "!svn/bc/" URL for a
> resource (especially now that it accepts public @-syntax URLs as
> input) and let people copy *that* and paste it into their browser than
> to have our server (which, by the way, has an open network protocol
> that anyone can use, as has been demonstrated by the likes of JavaSVN)
> complexify its very simple public URL schema and require all clients
> of mod_dav_svn to know about those intricacies.
>

The problem we had before was people becoming familiar
"!svn/bc/REV/path" after using it in a web browser for a while... and
then they'd go and use the same URL with 'svn cat' and get errors. Then
we'd hear complaints.

Should we just ignore this problem? Is it a non-problem? Or is there
just no acceptable solution to it?

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org