On Sat, Nov 21, 2009 at 02:55:21AM -0600, Ryan Schmidt wrote:
> On Nov 21, 2009, at 02:46, Ciprian Dorin, Craciun wrote:
>
> > Is there a restriction in the file names for Subversion (I have
> > version 1.6.5). Because I can not refer to files that have an `@`
> > character in their name. For example:
> > svn add ./something_at_somehost.com
> > says something like: `./somenting does not exist`
> >
> > But if I do `svn add --force .` then the file
> > `something_at_somehost.com` is added.
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3489
>
> says you need to escape the @ character because it is special to Subversion.
And it's even in the documented, not just the bug tracker:
Quoting http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html
The perceptive reader is probably wondering at this point whether the peg
revision syntax causes problems for working copy paths or URLs that actually
have at signs in them. After all, how does svn know whether news_at_11 is the name
of a directory in my tree or just a syntax for “revision 11 of news”?
Thankfully, while svn will always assume the latter, there is a trivial
workaround. You need only append an at sign to the end of the path, such as
news_at_11@. svn cares only about the last at sign in the argument, and it is not
considered illegal to omit a literal peg revision specifier after that at sign.
This workaround even applies to paths that end in an at sign—you would use
filename@@ to talk about a file named filename@.
It helps to read the book....
Stefan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2422728
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-21 12:59:41 CET