Op vrijdag 20 juli 2018 09:23:44 UTC+2 schreef Gordon Jess: > > Hi Nathan, > > Thank you for your suggestion and thorough explanation! I tried the > python script today and it worked great. > > The only downside of this method is that the folder structure of the > working copy must be the same that on the repository. Our SVN repository > structure is very much management orientated (organised by customer and > variation). SVN externals allowed us to specify a check-out structure more > suitable for development (e.g. organised by software architecture) >
As I said in my reply to Nathan: 'svn commit' nowadays has an option --include-externals, which will include any changes to (same repository) externals into the commit (unless they are "pegged" , i.e. pinned externals). So, again in reply to Nathan: yes, there is logic in the client-side commit machinery that resolves the external, discovers it is coming from the same repo, and performs one atomic commit. This feature has first appeared in 1.8.0. So Gordon, if you use version 1.8 or later of TortoiseSVN, it should be able to include externals in your commit (unless they are pegged externals). See this issue: https://issues.apache.org/jira/browse/SVN-1167 (Handle commits which include paths pulled in by svn:externals) And this mailinglist thread that's referenced by the above issue: https://svn.haxx.se/dev/archive-2011-08/0620.shtml Ah, I also found a reference to it in the 1.8 release notes: http://subversion.apache.org/docs/release-notes/1.8.html#commit-externals -- Johan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/b1a42a00-0df8-4158-b09f-2f1082b192a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
