Torsten Krah wrote on Mon, May 30, 2011 at 23:47:30 +0200: > Am Dienstag, den 31.05.2011, 00:30 +0300 schrieb Daniel Shahaf: > > then you could patch svnsync or one of those tools to do the > > recoding. (just inject a filename-recoding editor at the right place) > > Of cause i'll take the source, patch it and get my repo working > again ... nice joke - it was a joke right?
That's how I'd solve the problem. But then, I'm not a tech support person but a Subversion committer who is already familiar with FSFS and dumpstream format. Stefan Sperling wrote on Mon, May 30, 2011 at 23:54:17 +0200: > On Tue, May 31, 2011 at 12:30:54AM +0300, Daniel Shahaf wrote: > > then you could patch svnsync or one of those tools to do the > > recoding. (just inject a filename-recoding editor at the right place) > > Daniel, please keep in mind that this is the *users* list. > Maybe Torsten would like to try this, but I doubt that modifying > Subversion's code is the kind of advice he was looking for. > And I really don't think that this suggestion is something that people > who are not familiar with Subversion's code base should attempt to do. > If people modify the code without understand it well the chances of > unintentionally breaking things are way too high. > I'm usually very right-winged on telling people "Don't edit anything under $REPOS/db/ unless you can score A+ in an oral test on 'structure' at 3am." To the case at hand: * There is probably a tool that allows performing the needed conversion. * If there isn't, I think writing a "recode fspaths" filter to our API's isn't terribly hard (perhaps with some pointers on what API's to start at). What do you refer to by "breaking things"? > It's bad enough that Torsten has to edit the dump file to fix this. In the general case, I expect there to be Out There repositories that contain fspath's in multiple encodings: say, UTF-8 and latin1 (and possibly latin15 too) in the same filesystem. That's going to be a mess to fix no matter what tools you use.
