Re: cvs2git enforces SVN file naming on conversions

Daniel Hagerty <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
> From: Michael Haggerty <[email protected]>
 > Date: Tue, 31 Aug 2010 22:00:38 +0200
 >
 > Daniel Hagerty wrote:
 >
 >        ^^^^^^^ What kind of strange name is that? :-)

    Some crazy thing my parents came up with.  I'm pretty sure the
idea was to drive clerical workers used to the typical spelling just a
tiny bit more insane.  We all know how parents can be. :)

 > Indeed, git seems more tolerant of weird characters in filenames.
 > (Whether it is advisable to use such characters is another question :-) )

    I will readily grant you that the instances in this CVS repository
I'm working with appear more like "oops" than anything that genuinely
matters.

    However, it did make my life much easier when I didn't have to
fiddle with the source repository.

 > But in any case, your point that git is not so picky about filenames is
 > well taken.
 > [...]
 >
 > Unfortunately, your patches are against the 2.3.x branch of cvs2svn
 > rather than trunk, and don't apply to trunk.  Instead, I am working on a
 > solution that is somewhat more general, allowing for the possibility
 > that bzr and hg might have different rules:

    Yeah, 2.3.x is where I started from.  Sorry that what I offered
doesn't work for now, but it sounds like you're doing a much more
thorough job than I had done, anyway.

    Thanks for looking into this further!

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2654122

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.