On 2015-06-22 18.11, Junio C Hamano wrote:
Torsten Bögershausen tbo...@web.de writes:
eol=lf or eol=crlf are the only useful settings.
Everything else is ignored because it does not make sense.
See convert.c:
static enum eol git_path_check_eol()
That makes me wonder...
The original
Torsten Bögershausen tbo...@web.de writes:
eol=lf or eol=crlf are the only useful settings.
Everything else is ignored because it does not make sense.
See convert.c:
static enum eol git_path_check_eol()
That makes me wonder...
The original reasoning behind the current behaviour that we
On 06/21/2015 04:16 PM, Robert Dailey wrote:
On Sun, Jun 21, 2015 at 9:04 AM, Robert Dailey rcdailey.li...@gmail.com wrote:
Upon inspection of the gitattributes documentation page here:
https://git-scm.com/docs/gitattributes
When comparing the documentation for 'text' with 'eol', I see the
Upon inspection of the gitattributes documentation page here:
https://git-scm.com/docs/gitattributes
When comparing the documentation for 'text' with 'eol', I see the
following missing explanations for 'eol':
* eol
* -eol
Maybe the fact that these are missing means they are not valid to use.
On Sun, Jun 21, 2015 at 9:04 AM, Robert Dailey rcdailey.li...@gmail.com wrote:
Upon inspection of the gitattributes documentation page here:
https://git-scm.com/docs/gitattributes
When comparing the documentation for 'text' with 'eol', I see the
following missing explanations for 'eol':
*
5 matches
Mail list logo
