CVS->GIT with CRLF eols in the GIT repository
Gh Savulescu <[email protected]> Tue, 5 Nov 2013 20:18:20 +0200
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Hi all, I have a question about how to convert a "regular" CVS repository to a less "regular" GIT one. I am using cvs2git version 2.4.0 on Windows. The source CVS repo has all files properly marked text-or-binary. Text files are stored with LF line endings in the "*,v" files, and are checked out with CRLF eols. The less "regular" requirement for the GIT destination repo is to have core.autocrlf=false, no .gitattributes (nor .git/info/attributes), yet have text files checkout with CRLF line endings. For this, I suppose I need to have those files stored with CRLF eols in the GIT repository itself. So, the question: can I convince cvs2git to store text files in the destination GIT repo with CRLF eols as they are in a CVS checkout, and not with LF as they are in the source "*,v" files? If yes, how? I tried various --default-eol settings, notably "binary" and "CRLF", but when I chekout files from the resulting repo I still get LF if core.autocrlf=false; I get CRLFs only if I set core.autocrlf=true. In case someone is curios why I want this: I'm trying to use GitEye <http://www.collab.net/giteyeapp> which, if I understood correctly, is EGit/JGit separated from the rest of Eclipse and with some CollabNet stuff in. EGit/JGit do not implement .gitattributes, nor do they have a way to override the automatic text-vs-binary guesswork. And unsurprisingly that guesswork fails with some of my files so these get damaged if I set core.autocrlf=true. I have to set core.autocrlf=false, but then all text files are checked out with LF and I want CRLF (I'm on Windows). Thanks in advance for any help, sags ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3067932 To unsubscribe from this discussion, e-mail: [[email protected]].