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

Re: svn commit: rev 1643 - trunk/subversion/include trunk/subversion/libsvn_client trunk/subversion/clients/cmdline

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-04-06 00:36:44 CEST

cmpilato@collab.net writes:

> We could just keep the single '@' seperator, and if you have a file
> with '@' in the name itself, allow for "@@" escaping.
> Note the following paths at revision 123:
> foo -> foo@123
> foo@bar -> foo@@bar@123
> foo@123 -> foo@@123@123
> Of course, that means always un-escaping input paths, and the doom of
> using your shell's path completion (you'll have to insert extra '@'s),
> but...

My feeling is that on a Unix command line I would prefer using a
trailing @ like so:

  System Subversion Subversion
  Filename Filename Filename
                  at rev 123 no revision

  foo foo@123 foo
  foo@bar foo@bar@123 foo@bar@
  foo@999 foo@999@123 foo@999@
  foo@ foo@@123 foo@@

The decoder simply needs to examine the last delimiter:

   no @ character -> simple filename, no revision
   @ is last character -> strip last @ to get filename, no revision
   @ is not last character -> split at @ into filename and revision

Although since '@' is in use on my system (it's the standard delimiter
for locale name modifiers for one thing) I would prefer Subversion to
choose a different delimiter, perhaps '@@' leading to

  System Subversion Subversion
  Filename Filename Filename
                  at rev 123 no revision

  foo foo@@123 foo
  foo@bar foo@bar@@123 foo@bar
  foo@999 foo@999@@123 foo@999
  foo@ foo@@@123 foo@
  foo@@bar foo@@bar@@123 foo@@bar@@
  foo@@999 foo@@999@@123 foo@@999@@
  foo@@ foo@@@@123 foo@@@@

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 6 00:37:29 2002

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.