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

Confused about non-recursive behaviors

From: Guyren Howe <guyren_at_mac.com>
Date: 2006-12-14 21:46:39 CET

My

svn add *

is not descending into folders and adding files modified therein. I
have added said folders to my repository.

I've found threads, such as this one:

<http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=13832>

(from 2004, but that's what searching for 'recursive' finds).

The link above is to the immensely confusing reply, to whit:

I suspect the issue at hand is that your "includes" dir is already
controlled. Since you're just saying "svn add *" the "*" never
expands into
the subdirectories which are already controlled.

Say wha? I'm dying to hear how this comment makes sense. It seems to
suggest that if I want the contents of my project sub-directories
included in my repository, I should *not* add the directories! Huh?

I did find the --force option on the add command, and that did
descend into my subdirectories and find the changed files. But then,
when I do commit, I don't see the modifications.

Someone, somewhere, please explain why this is the sensible way for
things to work. There is clearly some bizarre assumption at work here
about how I'm supposed to treat my repository that I just don't get.

(Also, some options about how to fix this would be nice, too. Do I
svn delete my directories?)

Many thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 14 21:48:23 2006

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.