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

Re: Bug: IP address bogusly interpreted as peg revision

From: Jens Seidel <jensseidel_at_users.sourceforge.net>
Date: Mon, 26 May 2008 08:16:13 +0200

On Sun, May 25, 2008 at 09:45:56PM -0500, Troy Curtis Jr wrote:
> Behavior if we always use '@' for no peg specified:
> "." "@"
> "._at_BASE" "@BASE"
> "foo///bar" "foo/bar@"
> "http://a//b////" "http://a/b@"
> "http://a///b@27" "http://a/b@27"
> "http://a/b//@COMMITTED" "http://a/b@COMMITTED"
> "foo///@bar_at_HEAD" "foo/@bar_at_HEAD"
> "foo@///bar" "foo@/bar@"
> "foo_at_HEAD///bar" "foo_at_HEAD/bar@"
> Adding:
> "svn+ssh://svn@" "svn+ssh://svn@"
> "svn+ssh://svn@" "svn+ssh://svn@"
> "svn+ssh://svn@" "svn+ssh://svn@"

A stupid question: What would happen if there exists filenames with "@"
in it? Could there be a filename conflict if @ is added?

PS: There is no longer any need for CC:ing me. I'm currently subscribed.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-26 08:18:10 CEST

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.