Steve Williams wrote:
> From the Subversion Book on externals:
> http://svnbook.red-bean.com/en/1.0/ch07s03.html
> "if you want to commit changes that you've made in one or more of those
> external working copies, you must run svn commit explicitly on those
> working copies—committing on the primary working copy will not recurse
> into any external ones."
Thanks - I read that also, and it works.
But it kind of ruins the concept. The development team wants to be
able to click the top folder and do a 'Commit' of all the changes
they've done, without sifting through all the subfolders, figuring out
which ones of those have an 'svn:externals' property, and committing
them separately. In other words, the same ease as when using the
'Update' command on a top folder and updating all the externals also.
If the commit can't rescursively commit 'svn:externals' folders, what
advantage does it have over a simple script that checks out a bunch of
different paths?..
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Feb 23 11:46:53 2005