I'm running into this problem as well. Can you explain how I would use 
svndumpfilter to filter out the trash characters?

Thanks,
Phil

On Saturday, April 23, 2011 1:00:31 PM UTC-7, Konstantin Khomoutov wrote:
>
> On Sat, Apr 23, 2011 at 12:37:39PM -0700, Duff wrote:
>
> > I'm trying to import from another company's SVN server (with their
> > permission of course), however some of their SVN user entries have
> > carriage returns in them.  It causes git-svn to die when I use the --
> > authors-file option, because I can't add a username with a carriage
> > return in that file.  (Or can I?)
> > 
> > I see the following options, but I'd love more or easier ones.  Here
> > they are:
> > 
> > 1. Talk to the maintainer of the SVN server to remove the carriage
> > returns in the names.
> > 2. Edit git-svn.perl and recompile git.
> > 3. Skip the revisions that have the carriage return in them.
> > 4. Don't bother with the authors-file.
> > 
> > The SVN maintainer is a great guy but very busy, so I don't know when
> > he'll get to removing carriage returns, or if he'll agree to do so
> > anyway.  I'm using an IT controlled box, so I can't edit the /usr/bin/
> > git-svn file.  I switched to a box that I had control over, but the
> > version of git installed didn't have the /usr/bin/git-svn file at
> > all.  (I figure it's wrapped up into a single package now?)  So, I
> > tried to edit the git-svn.perl file in the source and recompile, but
> > I'm getting an error.
> Two ideas:
> * Removing bogus characters from committers' names is, indeed, a major
>   undertaking as it would involve "filtering" the actual repo using
>   Subversion's administration tools; so I can understand why the admin
>   is somewhat reluctant to work on this.  So, can you ask him/her to
>   just provide you with a dump of the original repo?  You then could
>   remove that trash characters yourself and then import the resulting
>   repo into Git without any hacks on the Git's side.
> * Perl is a scripting language which means it compiles the source file
>   just before executing the code in it, that is, on the fly.  Hence when
>   you change a .pl file there's absolutely no need to recompile
>   anything.  I mean, if you have a box you control (you can install Git
>   onto it), just patch the interesting file in place after getting
>   git-svn up and running.
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to