Mark Phippard wrote on Mon, Aug 22, 2016 at 17:06:05 -0400: > On Mon, Aug 22, 2016 at 2:11 PM, Eric Johnson <e...@tibco.com> wrote: > > > So I wrote myself a tool to go through all commit comments, and verify > > that no "CRs" appear in the svn:log entry. If I find them, I rewrite the > > log entry. That way, I can clean up existing repositories. > > > > However, I ran into a surprise. CR characters have also snuck into the > > svn:ignore property, which is *not* a revprop, and cannot be fixed by any > > of the tools available. > > > > I've seen that other people recommend editing the dump file directly, but > > that makes me quite nervous, especially on an 8MB dump file. Hoping there's > > a better way. > > > > Have you tried creating a new repository with the format you want and then > use svnsync to sync the data to it? I seem to recall that svnsync will fix > the line endings as it syncs the log entries. I could be wrong though > because I see that svnsync has a --source-prop-encoding option that we > added for fixing non UTF8 log messages. So it is possible I am confusing > with that option.
svnsync normalizes line endings to LF unconditionally. (sync.c:change_dir_prop() calls normalize_string())
