On 8/29/06, C. Michael Pilato <cmpilato@collab.net> wrote:
> [reposting this as a new thread]
>
> 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@{2006-03-05}
> 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.)
Well, all that occurs to me is "Good Question!" ;-)
I'm not sure if this was really thrashed out when we first added peg
revision support. Personally, I think it makes sense to assume that
it's part of the URI, so you'd unencode it before looking for the @,
but that's just off the top of my head, and I haven't actually looked
at the implementation to see what we're doing now.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 29 16:56:26 2006