All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvangeste <i.4m.l33t@yandex.ru>
To: git@vger.kernel.org
Subject: Re: [PATCH master] convert: The native line-ending is \r\n on MinGW
Date: Tue, 13 Aug 2013 17:44:35 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130813T193141-905@post.gmane.org> (raw)
In-Reply-To: loom.20130415T220316-790@post.gmane.org

Brice Lambson <bricelam <at> live.com> writes:
> +1, this is a significant issue downstream in Git for Windows:
> 
> https://github.com/msysgit/git/issues/57
> 
> Effectively this renders .gitattributes useless for the scenario of 
> enforcing normalized line ending characters.

+100

Folks, the problem is still there, with the very latest Git built with MinGW 
on Windows. Having eol=native in gitattributes means *LF* EOLs on 
Windows/MinGW.

So, essentially, eol=native is completely broken. And this is the most useful 
option to put into gitattributes and share among those working on the project.

Currently, I have to put eol=crlf there, and that means that those working on 
Linux will end up with CRLF files in their working copies.

The link quoted above does contain an additional fix that resolves the 
problem.

Thanks,
  --Tvangeste

  reply	other threads:[~2013-08-13 17:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 19:29 [PATCH v6] Add "core.eol" config variable Eyvind Bernhardsen
2010-09-04  8:25 ` [PATCH master] convert: The native line-ending is \r\n on MinGW Jonathan Nieder
2010-09-07  0:29   ` Junio C Hamano
2010-09-25 17:14     ` Ramsay Jones
2012-11-25 15:39     ` Mr_and_Mrs_D
2013-04-15 20:11       ` Brice Lambson
2013-08-13 17:44         ` Tvangeste [this message]
2013-08-13 18:03           ` Junio C Hamano
2013-04-15 21:00     ` Junio C Hamano
2013-04-15 21:20       ` Erik Faye-Lund
2013-04-15 21:43         ` Junio C Hamano
2013-04-16 14:39           ` Erik Faye-Lund
2013-04-16 18:03             ` Johannes Sixt
2013-04-16 18:26               ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20130813T193141-905@post.gmane.org \
    --to=i.4m.l33t@yandex.ru \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.