Agreed. It was dumb of me to even suggest it. The repo structure is way too convoluted to attempt such a thing.
On Thursday, 18 August 2022 at 6:56:19 pm UTC+10 daniel.. wrote: > torsdag 18 augusti 2022 kl. 04:07:21 UTC+2 skrev Phil Seakins: > >> After backing up the repository I would examine it with low level tools >> and once I found the slash I would change it to an X or a Y using a >> hexeditor such as Hxd. Might not work and there might be too many slashes >> to narrow it down but that would probably be my first angle of attack. >> Obviously Daniel's solution is much safer. >> > > I would really advice against editing the repository files manually. While > the files look human-readable, they are actually a very tightly defined > binary format. In particular, there may be references between different > files that are not obvious. Even if the repository is successfully updated > it might break existing working copies having the particular file checked > out. (That last argument is one of the reasons why it is difficult to purge > revisions from an SVN repository). > > Editing the repository files MIGHT be a last resort if there is really low > level data corruption and there is no other way to restore the data. > > Kind regards, > Daniel > >> -- 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/29c1f22e-9e45-43ed-a7d7-b148a5447573n%40googlegroups.com.
