All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>,
	git@vger.kernel.org,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH master] convert: The native line-ending is \r\n on MinGW
Date: Mon, 06 Sep 2010 17:29:08 -0700	[thread overview]
Message-ID: <7vbp8aqtuz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100904082509.GC10140@burratino> (Jonathan Nieder's message of "Sat\, 4 Sep 2010 03\:25\:09 -0500")

Jonathan Nieder <jrnieder@gmail.com> writes:

> If you try this:
>
>  1. Install Git for Windows (from the msysgit project)
>  2. Put
>
> 	[core]
> 		autocrlf = false
> 		eol = native
>
>     in your .gitconfig.
>  3. Clone a project with
>
> 	*.txt text
>
>     in its .gitattributes.
>
> Then with current git, any text files checked out have LF line
> endings, instead of the expected CRLF.
>
> Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
> Cc: Johannes Sixt <j6t@kdbg.org>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> ---
> Eyvind Bernhardsen wrote:
>
>> Introduce a new configuration variable, "core.eol", that allows the user
>> to set which line endings to use for end-of-line-normalized files in the
>> working directory.  It defaults to "native", which means CRLF on Windows
>> and LF everywhere else.
>
> The following fixup has been sitting in my tree (but not tested on
> Windows) for a couple of weeks.  Sensible?
>
> I don't know what the right choice for Cygwin is; probably LF unless
> there is some way to detect the systemwide setting at run time.

Has anybody in Windows land any input?  I don't think what I do before
1.7.3 in my tree would matter much, so I am not applying this myself.

  reply	other threads:[~2010-09-07  0:29 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 [this message]
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
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=7vbp8aqtuz.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=eyvind.bernhardsen@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=jrnieder@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.
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.