David, On Fri, Aug 27, 2010 at 3:59 PM, David H <evolveme...@gmail.com> wrote: > > 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. >
Its likely that you are seeing the result of the default global-ignores config value, described here: http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html --------------- global-ignores When running the svn status command, Subversion lists unversioned files and directories along with the versioned ones, annotating them with a ? character (see the section called “See an overview of your changes”). Sometimes it can be annoying to see uninteresting, unversioned items—for example, object files that result from a program's compilation—in this display. The global-ignoresoption is a list of whitespace-delimited globs that describe the names of files and directories that Subversion should not display unless they are versioned. The default value is *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo *.rej *~ #*# .#* .*.swp .DS_Store . As well as svn status, the svn add and svn import commands also ignore files that match the list when they are scanning a directory. You can override this behavior for a single instance of any of these commands by explicitly specifying the filename, or by using the --no-ignore command-line flag. ---------------- chris
