git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Brice Lambson <bricelam@live.com>
To: git@vger.kernel.org
Subject: Re: [PATCH master] convert: The native line-ending is \r\n on MinGW
Date: Mon, 15 Apr 2013 20:11:49 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130415T220316-790@post.gmane.org> (raw)
In-Reply-To: 1353857940941-7571889.post@n2.nabble.com

Mr_and_Mrs_D <the.ubik <at> gmail.com> writes:



> 

> I am on windows 7 Pro - mingwin

> 

> I decided to turn autocrlf to false and use .gitattributes instead and was

> bitten by this bug :

> 

> http://stackoverflow.com/questions/13531988/git-line-endings-renormalize-
does-not-seem-to-checkout-the-right-line-endings

> 

> It took me 2 days to figure this out

> 

> Please fix

> 

> --

> View this message in context: http://git.661346.n2.nabble.com/PATCH-v6-
Add-core-eol-config-variable-tp5140844p7571889.html

> Sent from the git mailing list archive at Nabble.com.

> 



+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.

  reply	other threads:[~2013-04-15 20:20 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 [this message]
2013-08-13 17:44         ` Tvangeste
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=loom.20130415T220316-790@post.gmane.org \
    --to=bricelam@live.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).