On Friday, July 20, 2018 at 3:23:44 AM UTC-4, Gordon Jess wrote: > > 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) >
Yes that is a pretty big downside. On further thought, it also probably affects your ability to build the code, because (1) your build system expects to find things in the locations specified by the externals, and (2) if you are using pegged externals, simply doing a sparse checkout of the whole repository will give you the HEAD revision, whereas the pegged externals might be specifying older versions. One more thing... can you please further explain this comment? > > >Be mindful to be in the topmost directory when doing so, > >as Subversion commits apply to the current directory and > >all nested directories under it. > > What would be the problem with committing from a nested directory, as long > as it contains all the parts I want to commit? > That's what I meant: In order to get the atomic commit you want, you need to be in a directory that contains all the parts you want to commit. -- 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/2535b237-1262-45cf-b876-9437a09526fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
