Re: autocrlf=input and safecrlf (was Re: CVS import [SOLVED])
> 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)
Ferry Huberts (Pelagic) <ferry.huberts@pelagic.nl>