How does the core.autocrlf config setting interact with how the repository is mounted? If I mounted the repository binary, but set core.autocrlf to translate lf to crlf, would my data files still translate to crlf endings when I pull from a Linux repository to Windows, while retaining lf endings when I pull the same repository to a Linux box?
That is the functionality that I need. Peter K. ------------------------------------------------------------------------ Peter Klavins Datalon SrL [EMAIL PROTECTED] Viale Giuseppe Mazzini 114/A Mobile +39 339 801 4246 Fax +39 06 233 297 037 00195 Roma RM Italy > -----Original Message----- > From: Eric Blake [mailto:[EMAIL PROTECTED] > Sent: Sunday, 23 September 2007 4:41 PM > To: cygwin@cygwin.com; [EMAIL PROTECTED] > Subject: Re: git on cygwin howto? > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Peter Klavins on 9/23/2007 7:21 AM: > > Could someone please help me use git on cygwin? Ah, by the way, I > use > > DOS line ends on cygwin, i.e., \r\n not \n like on Linux. Could that > be > > the problem? If so, then maybe it's something cygwin git could be > aware > > of? > > That is exactly the problem. Git won't work if spurious \r appear in > the > files, which is what happens on a text mount when a file is created in > text mode and reopened in binary mode. Mount your git repository on a > binary mount instead. A patch was already proposed upstream to make > git.exe always open files in binary mode, but I don't know whether it > was > ever accepted, and even if it was, it doesn't help for those git > actions > which are still independent scripts instead of built into git.exe. I > suppose that next time I try a release, I could spend more time trying > to > support text mode, but it isn't my highest priority, because git > contains > so many disparate tools that would all need auditing. > > - -- > Don't work too hard, make some time for fun as well! > > Eric Blake [EMAIL PROTECTED] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Cygwin) > Comment: Public key at home.comcast.net/~ericblake/eblake.gpg > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFG9nr384KuGfSFAYARAu42AJ9q6itWWXOqTx3rXekSqyLk1dwfvACeIE5y > Fpx89y11gZ2QrWLWtwhx9gc= > =W2TC > -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME cryptographic signature
