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

RE: "svn add *" and <at> sign in filename

From: Варфоломеев Игорь <i3v_at_mail.ru>
Date: Wed, 10 Jul 2013 04:39:23 +0400

> From: 'Daniel Shahaf' [mailto:d.s_at_daniel.shahaf.name]
> Sent: Wednesday, July 10, 2013 4:25 AM
>
> Варфоломеев Игорь wrote on Wed, Jul 10, 2013 at 04:17:37 +0400:
> > From: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> > >
> > > Run 'svn add wc/B_at_2.txt@'.
> >
> > Did you mean "svn add wc\B\@2.txt@" ?
>
> Forward and backward slashes are interchangeable when using svn on
> windows.

They are... I've only meant that "svn add wc/B_at_2.txt@" lacks a slash after "B"...
The interesting thing is - this is exactly how it's displayed in an error message:

----------------------------------------
> In particular
> svn add wc\B\*
> results in
> svn: E200009: 'wc/B_at_2.txt': a peg revision is not allowed here if
> there's a file "@2.txt" inside "B".
----------------------------------------
 
> Just do: svn add wc\B
>
> (if B is alreadyed versioned, add --force to that command)

This works, yep. But this looks more like a workaround (in case "B" itself is already versioned).
I don't say this is a critical bug, but I think if "svn add wc\B\*" syntax is working in one case,
It should work in all cases, independently of directory contents....
Received on 2013-07-10 02:40:05 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.