Re: autocrlf=input and safecrlf (was Re: CVS import [SOLVED])
- From
Jeff King <peff@peff.net>
- Date
- Feb 23, 2009, 06:56 UTC
- Message-ID
- <20090223065615.GA24807@coredump.intra.peff.net>
- In-Reply-To
- <2944.77.61.241.211.1235371848.squirrel@hupie.xs4all.nl>
[Can you please wrap your lines? They seem to be about 200 characters, and then rewrap the quoted text, but without putting a '>' marker. I had a very hard time figuring out what was quoted and what was not.]
On Mon, Feb 23, 2009 at 07:50:48AM +0100, Ferry Huberts (Pelagic) wrote:
Show 8 quoted lines
> > I am a bit concerned about a proposal to set safecrlf=false in all > > cvsimported repositories. You are turning off the protection > > against corrupting binary files. _Even if_ the person has put > > safecrlf=true into their ~/.gitconfig and thinks they are safe. > > Ok. I follow and agree. Full circle :-) We're back to Johannes' > proposal: make sure that autocrlf is set to false. Agree? If so, then > I'll try to whip up a patch.
But won't that now import CRLF's into your new git repo? Especially on Windows, where (IIRC) cvs gives you files with CRLF by default?
-Peff