[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: Aaron Sher <asher_at_vanteon.com>
Date: 2005-08-08 15:43:38 CEST

Apologies - I just investigated this a bit more closely and I discovered
that this behavior is an artifact of the way that I'm using svn. I have a
shell script that's wrapping svn (for the purpose of handling resource forks
on the Mac), and that changes the behavior of this case.

The actual behavior is consistent - both "svn status" and "svn commit"
complain that there's no file named "test.*" if the shell can't expand the
pattern. Whether this is actually the right behavior or not, I'm not going
to speculate, but there doesn't (now) seem to be a bug here.


> -----Original Message-----
> From: Kevin T. Broderick [mailto:kbroderick@smcvt.edu]
> Sent: Sunday, August 07, 2005 12:04 PM
> To: users@subversion.tigris.org
> Cc: asher@vanteon.com
> Subject: Re: Using wildcarded file names
> 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 Mon Aug 8 15:46:40 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.