On Mon, May 10, 2010 at 12:13:58PM +0400, Dmitry Potapov wrote:
quoted text
> 
> First of autocrlf is safe as it is implemented now.

No, it isn't. autocrlf as it is implemented now is destructive for any
file that contains CRLF in the repo (it also gives dirty files after
checkout and so on).

quoted text
> I believe that the right solution is to be able to enable autocrlf but
> only for those repositories that are marked as autocrlf compatible by
> upstream.

Yes absolutely. But how do you tell autocrlf that the repository is
compatible with it?  This is what is causing all the problems.

Now, I propose to change autocrlf in such a way that it will work as
before for all repositories that are "compatible with it", but _also_
so that it works reasonably with those that aren't.

- Finn Arne
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html