From: Junio C Hamano <gitster@pobox.com>
To: Tvangeste <i.4m.l33t@yandex.ru>
Cc: git@vger.kernel.org, Erik Faye-Lund <kusmabite@gmail.com>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH master] convert: The native line-ending is \r\n on MinGW
Date: Tue, 13 Aug 2013 11:03:49 -0700 [thread overview]
Message-ID: <7vioz9wjqy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <loom.20130813T193141-905@post.gmane.org> (Tvangeste's message of "Tue, 13 Aug 2013 17:44:35 +0000 (UTC)")
Tvangeste <i.4m.l33t@yandex.ru> writes:
> 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.
The patch in the thread you are responding to is v1.8.3-rc0~65, so
as far as the upstream git.git is concerned the issue is closed, but
I cannot say that inter-project coordination between us and Git for
Windows are stellar (no we are not fighting against each other, but
being less intimate with what the other is doing than we could be).
Judging from how the original thread ended:
http://thread.gmane.org/gmane.comp.version-control.git/148436/focus=221438
Eric and J6t (cc'ed) are aware of this patch that went into 1.8.3,
so...
next prev parent reply other threads:[~2013-08-13 18:04 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
2013-08-13 18:03 ` Junio C Hamano [this message]
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=7vioz9wjqy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=i.4m.l33t@yandex.ru \
--cc=j6t@kdbg.org \
--cc=kusmabite@gmail.com \
/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).