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

Bug report: wild-cards in command-line

From: Charles Engelke <tortoisesvn_at_engelke.com>
Date: Wed, 25 Jan 2012 11:00:37 -0800 (PST)

This affects the command line "svn" tools.

The svn update and svn propset commands do not accept wild-cards. Other Subversion command line clients I have tried (Collabnet, SlikSvn, and Linux svn) all do accept them.

Example:

Try to set the end-of-line property on all files in a directory:

   svn propset svn:eol-style native *

Fails with:

   '*' is not under version controlsvn: E155010: The node 'somepathendingwith\*' was not found.

Similarly, try to update many working copies in a common folder:

   svn up *

Fails with:

   Skipped '*'
   Summary of conflicts:
     Skipped paths: 1

Other command-line clients each treat the wild-card as if a list of all matches had been specified. This one is treating it like a literal filename.

I do not know whether other subcommands also act this way. These are the two that I often use wild-cards with.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2911103

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-25 20:05:39 CET

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

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