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

Re: Filenames containing '@' symbol

From: Sviataslau Svirydau <Sviataslau_Svirydau_at_epam.com>
Date: 2005-12-21 21:01:18 CET

You are right, adding explicit revision helps.
However, It is needed for 'proplist' and 'propget' commands, but fails
with 'propset' :) It is not required to add @ for 'propset' and
'propedit' commands when executing it on working copy. Moreover,
proplist and propget require revision for working copy, but doesn't
handle it! Just info for working copy is returned.

So, I think 'proplist' and 'propget' commands should work in the same
way with working copy as 'propset' and 'propedit'.

My original concern was about svn_load_dirs.pl. It was failed when using
'svn proplist'... If proplist and propget commands are fixed, it will
not be needed to fix svn_load_dirs.pl, otherwise, some workaround needed.

Phillip Susi wrote on 12/21/2005 9:26 PM:
> The problem isn't the shell, the @ character isn't treated specially
> by it AFAIR. The problem is that svn treats the @ as a peg revision.
>
> Try appending an explicit peg revision to the end of the name. I
> think svn will parse the last one as the peg revision, and earlier @'s
> as part of the name.
>
> Gale, David wrote:
>> Try putting a backslash before the @ signs. (bash's tab-completion
>> should automatically do this; I'm not sure about wildcard expansion.)
>> Alternatively, you could try enclosing the file name in single quotes,
>> but I'm not as sure that that would work.
>>
>> -David

-- 
Best Regards,
Sviatoslav Sviridov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 01:36:55 2005

This is an archived mail posted to the Subversion Users mailing list.