An idea: The problem can be solved similarly to what windows does because of the spaces in filenames. In the rare cases when the space would cause ambiquity one can quote the path. For example: "foo@the"@456, or foo@123 and foo@123.
----- Original Message -----
From: Ben Collins
To: Philip Martin
Cc: dev@subversion.tigris.org
Sent: Friday, April 05, 2002 8:09 PM
Subject: Re: svn commit: rev 1643 - trunk/subversion/include trunk/subversion/libsvn_client trunk/subversion/clients/cmdline
On Fri, Apr 05, 2002 at 07:57:26PM +0100, Philip Martin wrote:
> sussman@tigris.org writes:
>
> > Make client application parse 'svn merge' args correctly. This is just a
> > first run. Karl suggests that we extend the "PATH@REV" syntax to
> > *all* subcommands that can use it (diff, copy, etc.) That will be my
> > next changeset, if possible.
>
> I haven't seen much discussion about this feature. There are 75 files
> on my system that include an '@' character in their name. Those are
> all system files, and I am unlikely to want to version them, but file
> names including an '@' do occur. Several of the common locales include
> an '@' character in their name.
>
> Perhaps we should follow Clearcase and use '@@', if only because the
> fewer special sequences that are in use in the world, the better.
perforce uses "@". I think this can be easily handled by stating for the
full name first, and then chop off the "@.*" if that full name doesn't
exist. Then you have a problem with a file called "foo" and "foo@123", if
you want to see rev 123 of "foo". We have problems no matter what
though.
Ben
--
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 5 22:18:05 2002