Re: [PATCH v3 1/6] Fix build with core.autocrlf=true

Hi, On Tue, 23 May 2017, Junio C Hamano wrote: > Jonathan Nieder writes: > > > Junio, how do you prefer to handle this in git.git? Would you need to > > amend the patch to remove the git-gui/.gitattributes change and wait > > to get it from Pat, or is getting the same

Re: [PATCH v3 1/6] Fix build with core.autocrlf=true

Jonathan Nieder writes: > Junio, how do you prefer to handle this in git.git? Would you need to > amend the patch to remove the git-gui/.gitattributes change and wait > to get it from Pat, or is getting the same change twice okay? Yes, getting the same change twice should

Re: [PATCH v3 1/6] Fix build with core.autocrlf=true

(+cc: Pat Thoyts, git-gui maintainer) Hi, Johannes Schindelin wrote: > On Windows, the default line endings are denoted by a Carriage Return > byte followed by a Line Feed byte, while Linux and MacOSX use a single > Line Feed byte to denote a line ending. > > To help with this situation, Git

[PATCH v3 1/6] Fix build with core.autocrlf=true

On Windows, the default line endings are denoted by a Carriage Return byte followed by a Line Feed byte, while Linux and MacOSX use a single Line Feed byte to denote a line ending. To help with this situation, Git introduced several mechanisms over the last decade, most prominently the