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

Clearing up some API ambiguity (Was: Revision dates in URLs)

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2006-08-28 23:10:14 CEST

Looking at svn_opt_parse_path(), it's not clear to me how to interpret
the following input paths to that function:

   http://server/repos/path@%7B2006%2d03%2D05%7D ({2006-03-05}, encoded)
   http://server/repos/path@%48%45%41%44 (HEAD, encoded)

In fact, it occurs to me that, in general, I don't understand if we
consider the @-and-stuff-that-follows-it to be part of the path, or just
some unencoded bits we slap onto the end of properly-formatted paths as
a way to flatten otherwise tabular input data at the command-line UI.

What about when the @ symbol itself is URI-encoded. Does that mean
something different from when it is not?

(Sorry. I feel like I should know the answer here already, but if I do,
it's crouching in some dark corner in the back of my mind.)

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Mon Aug 28 23:11:20 2006

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.