[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Fwd: Re: Official revision syntax for Subversion URLs

From: Marc Haisenko <haisenko_at_webport.de>
Date: 2003-08-05 19:03:19 CEST

Forgot to CC: the devlist ...

---------- Forwarded Message ----------

Subject: Re: Official revision syntax for Subversion URLs
Date: Tuesday 05 August 2003 19:00
From: Marc Haisenko <haisenko@webport.de>
To: John Peacock <jpeacock@rowman.com>

On Tuesday 05 August 2003 18:05, John Peacock wrote:
> Robert Spier wrote:
> > To get to the fifteenth version of that file (on the main branch)
> > you'd refer to:
> > foo@@bar@@baz@@/main/15
>
> Except that with subversion, you have already specified the branch itself,
> before you specify the path/filename you are interested in. Personally, I
> have to agree with the earlier suggestion to tying the revision request to
> the repository:
>
> http://svn.host/path/to/repository@16254/path/to/file
>
> which has the added advantage that the character '@' only has to be
> forbidden from the repository path name itself (instead of random
> files/directories within the repository).
>
> My 2 cents
>
> John

AFAIK this would make a http connection to 16254/path/to/file as user
svn.host/path/to/repository. If I'm not completely mistaken everything before
an @ in a http path is a username/password to logon, like this:
http://user:password@host

Finding the necessary delimiter character may prove difficult

--
Marc Haisenko
Systemspezialist
Webport IT-Services GmbH
mailto: haisenko@webport.de
-------------------------------------------------------
-- 
Marc Haisenko
Systemspezialist
Webport IT-Services GmbH
mailto: haisenko@webport.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 5 19:05:14 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.