Re: Draft of Git Rev News edition 33

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Nov 21, 2017, 01:10 UTC
Message-ID: <20171121011017.e2aac53zfo2n2whc@aiede.mtv.corp.google.com>
In-Reply-To: <CAJYFCiOj1DwgMMrFRxV315CB7xuvXMFRbRAkbx6s14oPm3ui1Q@mail.gmail.com>

Hi,

Yubin Ruan wrote:

> 2017-11-20 16:33 GMT+08:00 Christian Couder <christian.couder@gmail.com>:

Show 11 quoted lines

>> A draft of a new Git Rev News edition is available here:
>>
>>   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-33.md
>>
>> Everyone is welcome to contribute in any section either by editing the
>> above page on GitHub and sending a pull request, or by commenting on
>> this GitHub issue:
>>
>>   https://github.com/git/git.github.io/issues/262
>>
>> You can also reply to this email.

[...]

> For the CRLF issue: I am not really that concerned with this issue
> because I mostly develop all my project on Linux. But can't git treat
> CRLF and LF just as the same thing? That will solves the problem
> gracefully.

Do you mean that it should ignore line ending changes? What line endings should a user get when they "git clone" or "git checkout"?

That said, I believe that the gitattributes(5) manpage does an okay job of covering this and that that thread came to a clear conclusion:

  https://public-inbox.org/git/20171026203046.fu3z5ngnw7hckfrn@aiede.mtv.corp.google.com/

I commented at [1] that I found the conclusion of the rev news entry misleading and confusing but it doesn't appear that there is anything I can do about that. It's disappointing because if there is something that was not covered in that thread, then it would be good to revive it so we can improve the program's behavior or docs, but I wasn't able to find out what was missed.

Thanks, Jonathan

[1] https://github.com/git/git.github.io/issues/262#issuecomment-345804038