On Thu, Jul 14, 2022 at 9:44 AM Daniel Shahaf wrote:
>
> Ryan Schmidt wrote on Wed, 13 Jul 2022 21:45 +00:00:
> > [...] that way all your public users' working copies continue to work
> > as before, and you would just need to check out new working copies for
> > those hopefully fewer and more tech
Hi Daniel,
Thanks for elaborating. I agree this network disconnection issue is a truly
minor one. At the same time Nathan mentioned several other occurrences of the
same issue. So maybe the sum of all information eventually allows TSVN to get
this exception handled for the more common use cases
Den ons 13 juli 2022 kl 15:35 skrev Klaey Matthias LCPF-CH <
matthias.kl...@mt.com>:
> Hi Nathan,
>
> See my responses further below as [MK 2022-07-13: ].
>
> Not sure whether my email properly has the [In-Reply-To] filled-in to end
> up in https://lists.apache.org/thread/n5vo9kznz9z2gzwy7kym9nj5r
On 7/13/2022 9:25 AM, Daniel Shahaf wrote:
Thorsten Schöning wrote on Mon, Jul 11, 2022 at 16:06:11 +0200:
Do you have any tips for the easiest possible change of the UUIDs?
It'll be a lot easier to set the repository's UUID to the one expected
by clients. See «svnadmin setuuid».
This is wh
Ryan Schmidt wrote on Wed, 13 Jul 2022 21:45 +00:00:
> [...] that way all your public users' working copies continue to work
> as before, and you would just need to check out new working copies for
> those hopefully fewer and more technically capable internal users who
> were using the formerly pri
