a suggestion

[David H <ev...@gmail.com>]

Subversion Dev team:

Thanks for all your hard work. I just began using subversion and it is
great.

Among other things, it is fast.

One complaint.

As a new user it was my expectation that 'svn add *' called from within the
root
of my version-controlled root directory would result in *all* changes that
had been
made within the file system to be scheduled for inclusion on the next
commit.

Instead, it ignored a whole raft of new files that were buried in
subdirectories.

It took me a while of poking around to find this out.

The behavior I expected was that "svn add *" would schedule a snapshot of
the
entire directory tree. Of course, to actually make this happen, I had to use
the "svn add * --force"
option.

Why would you have subversion skip a bunch of files? That makes no sense.

It seems to me, the default behavior should be the obvious behavior. Or
maybe there
is more that I don't yet understand. If so, I would like to hear.

Thanks. It is great software.

David Heitzman

-- 
Life moves on, whether we act as cowards, or heroes.

Re: a suggestion

[Alexey Neyman <st...@att.net>]

Hi David,

First, I think usage questions are better directed to 
users@subversion.apache.org list.

As to your question: the asterisk (*) you pass as an argument is, most 
probably, not even seen by Subversion. Instead, it is expanded to the actual 
list of files and directories by your shell. While expanding asterisk, shell 
usually omits files starting with dot. So, if you have

foo/
  foo1.c
  foo2.c
.bar/
  bar1.c
.baz.c
boom.c

in your working copy, "svn add *" will be passed to Subversion as "svn add foo 
boom.c". Hence, .bar directory and .baz.c file will not be added.

[The above assumes Linux/Unix environment. Things may be different on Widows]

Hope that helps,
Alexey.

On Thursday, August 26, 2010 08:46:21 pm David H wrote:
> Subversion Dev team:
> 
> Thanks for all your hard work. I just began using subversion and it is
> great.
> 
> Among other things, it is fast.
> 
> One complaint.
> 
> As a new user it was my expectation that 'svn add *' called from within the
> root
> of my version-controlled root directory would result in *all* changes that
> had been
> made within the file system to be scheduled for inclusion on the next
> commit.
> 
> Instead, it ignored a whole raft of new files that were buried in
> subdirectories.
> 
> It took me a while of poking around to find this out.
> 
> The behavior I expected was that "svn add *" would schedule a snapshot of
> the
> entire directory tree. Of course, to actually make this happen, I had to
> use the "svn add * --force"
> option.
> 
> Why would you have subversion skip a bunch of files? That makes no sense.
> 
> It seems to me, the default behavior should be the obvious behavior. Or
> maybe there
> is more that I don't yet understand. If so, I would like to hear.
> 
> Thanks. It is great software.
> 
> David Heitzman