From: Stephen Bash <bash@genarts.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: Git EOL Normalization
Date: Thu, 26 May 2011 12:28:48 -0400 (EDT) [thread overview]
Message-ID: <22629514.41388.1306427328539.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <7v1uzlzbra.fsf@alter.siamese.dyndns.org>
----- Original Message -----
> From: "Junio C Hamano" <gitster@pobox.com>
> To: "Jakub Narebski" <jnareb@gmail.com>
> Sent: Thursday, May 26, 2011 12:07:21 PM
> Subject: Re: Git EOL Normalization
>
> > I think git examines only first block of a file or so. The heuristic
> > to detect binary-ness of a file is, as I have heard, the same or
> > similar to the one that GNU diff uses.
>
> Yes, the binary detection was designed to be compatible with GNU diff. But
> I do not think it has much to do with the topic of this thread. Aren't
> other people discussing the line ending?
The binary detection may be apropos because there are situations (core.autocrlf={true,input} and text=auto) where Git will only do line ending conversion if it detects a text file... But I'll leave it to people who know the code better to say if this binary detection is in fact part of the decision process.
Thanks,
Stephen
next prev parent reply other threads:[~2011-05-26 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20833035.39857.1306334468204.JavaMail.root@mail.hq.genarts.com>
2011-05-25 15:20 ` Git EOL Normalization Stephen Bash
2011-05-25 17:58 ` Dmitry Potapov
2011-05-25 18:06 ` Stephen Bash
2011-05-26 6:02 ` Jakub Narebski
2011-05-26 7:20 ` Dmitry Potapov
2011-05-26 16:07 ` Junio C Hamano
2011-05-26 16:28 ` Stephen Bash [this message]
2011-05-31 15:01 ` Drew Northup
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=22629514.41388.1306427328539.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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 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 NNTP newsgroup(s).