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

Re: Using wildcarded file names

From: Kevin T. Broderick <kbroderick_at_smcvt.edu>
Date: 2005-08-07 18:03:42 CEST

On 7 Aug 2005, at 11:59 AM, Kevin T. Broderick wrote:

> On 5 Aug 2005, at 10:26 AM, Aaron Sher wrote:
>> Here’s a funny corner case that I believe exposes a bug (I’m
>> running on Mac OS X with version 1.2.1):
>> Add a file named test.txt to the repository (“svn add test.txt”)
>> Remove the file (“svn remove test.txt”)
>> Commit the change, using a wildcard (“svn commit test.*”)
>> This works properly. However, if instead of committing the change,
>> you try to request status with a wildcard (“svn status test.*”),
>> it doesn’t work. I think this should be consistent – either way
>> would make sense, but status and commit should handle this case in
>> the same way. What does everybody else think?
> Subversion isn't handling the wildcard, the shell is. So the
> actual commands being executed are:
> "svn commit"
> vs
> "svn status"
> (Unless, of course, there are other files matching the wildcard
> test.* in the same directory)
> If it helps, look at the output of
> echo svn commit test.*
> echo svn status test.*
> (svn status displays nothing if the input does not describe a
> versioned file)

OK, not quite. I guess svn is doing the wildcard expansion, but it's
doing the wildcard expansion before passing parameters to
subcommands. So "svn status test.*", when no files in the directory
match that wildcard, gets expanded to "svn status"; "svn commit
test.*" is likewise.

Kevin Broderick / kbroderick@smcvt.edu

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 7 18:05:30 2005

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.