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

add * ignores new files in subdirectories.

From: David H <evolvemeans_at_gmail.com>
Date: Fri, 27 Aug 2010 14:59:26 -0500

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.

I'm using a Linux system, fyi.

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. It's also worth noting that the option "svn add * --depth infinity"
also did not add the files that were
buried in the subdirectores; they were not added to be included on the next
commit.

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

The "import" command conversely, adds all the files in all the
subdirectories, when a new directory
is first brought under version control.

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.
Received on 2010-08-27 22:02:54 CEST

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.