From: Ferry Huberts (Pelagic) Date: Tue, 24 Feb 2009 09:25:12 GMT Subject: Re: autocrlf=input and safecrlf (was Re: CVS import [SOLVED]) Message-ID: <14283.77.61.241.211.1235467512.squirrel@hupie.xs4all.nl> In-Reply-To: <20090224061134.GF4615@coredump.intra.peff.net> > So yes, in some sense it is safecrlf that is broken. I'm just concerned > about tweaking the user's options behind their back. The import can > happen differently than they expected no matter which of safecrlf or > autocrlf you tweak. So I think you are better off to complain and die. The plan was: - when creating a new git repo for cvs import: setup safecrlf=false - when importing into an existing repo: check whether the safecrlf setting is set to false and crash and burn when not :-) (complain before going up in flames)