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

Re: 1.7.x bug - svn add no longer accepts wildcards?

From: Daniel Becroft <djcbecroft_at_gmail.com>
Date: Tue, 30 Nov 2010 22:02:55 +1000

On Tue, Nov 30, 2010 at 7:18 PM, Branko Čibej <brane_at_xbc.nu> wrote:
>
> On 30.11.2010 05:32, Daniel Becroft wrote:
> > Hi,
> >
> > During testing of a 1.7.x build, I've noticed that 'svn add' on trunk no
> > longer accepts wildcards:
> >
> > svn 1.6.x:
> > D:\temp\svn_sandpit\workingcopy\trunk\A>echo 1111111 1>alpha.txt
> > D:\temp\svn_sandpit\workingcopy\trunk\A>echo 1111111 1>beta.txt
> > D:\temp\svn_sandpit\workingcopy\trunk\A>svn add *.txt
> > A alpha.txt
> > A beta.txt
> >
> > Whereas 1.7.x gives:
> > D:\temp\svn_sandpit\workingcopy\trunk\A>echo 1111111 1>alpha.txt
> > D:\temp\svn_sandpit\workingcopy\trunk\A>echo 1111111 1>beta.txt
> > D:\temp\svn_sandpit\workingcopy\trunk\A>D:\temp\svn_sandpit\svn7.exe
> add
> > *.txt
> > svn: warning: 'D:\temp\svn_sandpit\workingcopy\trunk\A\*.txt' not
> found
> >
> > I thought that wildcards were expanded by the OS/Shell, and then passed
> to
> > SVN. Is this not the case?
>
> Not on windows, you have to link a magic library into your code to get
> that behaviour.
>
> -- Brane
>

Hmm ... that makes sense. My two separate EXEs were obtained from two
separate sources, so obviously the 1.6.x version links this 'magic library'.

I don't suppose you can tell me which library, so I can see if that's
included in the 1.7.x build?

Cheers,
Daniel B.
Received on 2010-11-30 13:03:52 CET

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