On Thursday, July 19, 2018 at 4:33:30 AM UTC-4, Johan Corveleyn wrote:
>
> Op woensdag 18 juli 2018 17:38:05 UTC+2 schreef Nathan Hartman:
>>
>> One more thing: I didn't answer your original question, which is: why 
>> can't you do an atomic commit that recurses into externals?
>>
>> If I understand correctly, this is the reason: svn:externals may fetch 
>> from multiple different repositories, even potentially located on different 
>> servers in different geographic regions. In your case, you are fetching all 
>> externals from the same repository, ...
>>
>
> I'm confused. As far as I know, performing an atomic commit that includes 
> externals (from the same repository) should work. Even performing a commit 
> that includes externals from other repositories should work from the UI 
> (but it won't be atomic, of course, it will perform different commits per 
> repository, under the hood).
>
> At least, on the commandline, 'svn commit' has an option 
> --include-externals:
>   --include-externals      : also operate on externals defined by
>                              svn:externals properties
>
> Maybe the OP is using an old version of TortoiseSVN? I'm not sure in which 
> svn version the --include-externals option for 'commit' was introduced.
>
>
I think I'm the one who's confused.

But I'll quote the svn-book (r5320) -- "Perhaps most disappointingly, the 
working copies created via the externals definition support are still 
disconnected from the primary working copy (on whose versioned directories 
the svn:externals property was actually set). And Subversion still truly 
operates only on nondisjoint working copies. So, for example, 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."

Of course, that was for svn 1.7. Much has changed since then (such as 
--include-externals).

You're saying 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? If that's the case then I'm really glad to hear 
that! That can simplify things for us and for the OP considerably.

-- 
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/bf63e5e7-14a6-4d47-b6c4-766936156b8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • committin... tortoisesvn+APn2wQf03iZ27psqyjVgcl_WqjGHKiM8YbJ5EIvDseIq3iyr4wjn
    • Re: ... Nathan Hartman via TortoiseSVN
    • Re: ... Nathan Hartman via TortoiseSVN
      • ... Johan Corveleyn via TortoiseSVN
        • ... Nathan Hartman via TortoiseSVN
    • Re: ... tortoisesvn+APn2wQf03iZ27psqyjVgcl_WqjGHKiM8YbJ5EIvDseIq3iyr4wjn
      • ... Johan Corveleyn via TortoiseSVN
        • ... Nathan Hartman via TortoiseSVN
      • ... Nathan Hartman via TortoiseSVN

Reply via email to