Thanks for the info, it helps.
> # touch includes/test.php
>
> # svn status
> ! temp/productlist1_Working_Model.csv
> ? includes/test.php
> ? admin/configuration.php.merc
>
> # svn add *
> svn: warning: 'about.php' is already under version control
> svn: warning: 'account.php' is already under version control
> svn: warning: 'account_edit.php' is already under version control
> svn: warning: 'guarantee.php' is already under version control
> svn: warning: 'images' is already under version control
> svn: warning: 'importfiles' is already under version control
> svn: warning: 'includes' is already under version control
> svn: warning: 'index.html' is already under version control
> svn: warning: 'index.php' is already under version control
> svn: warning: 'info_shopping_cart.php' is already under
> version control
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.
I'm going to try to replicate this behaviour using my test repository a
little later today - but even if I can I'm not sure I'd consider this a bug,
per se. FYI, the way I handle this sort of thing: I wrote a wrapper around
"svn ci" which does "svn st", looks for '!' and '?' entries, then proceeds
to annoy the user about them. I can post the code if you're interested.
(One of the prerequisites to my wrapper script being useful, though, is
judicious and thorough use of the svn:ignore property on the working copy.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 8 17:55:37 2004