From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff: treat -crlf files as binary
Date: Fri, 29 Aug 2008 17:56:38 -0400 [thread overview]
Message-ID: <32541b130808291456k3de953a2yd1e93bc27ad14293@mail.gmail.com> (raw)
In-Reply-To: <7vfxon4ikr.fsf@gitster.siamese.dyndns.org>
On Fri, Aug 29, 2008 at 5:28 PM, Junio C Hamano <gitster@pobox.com> wrote:
> The manual advertises that setting "crlf" attribute to false marks the
> file as binary. We should pay attention to this condition in addition
> to the "do not diff" attribute (i.e. setting "diff" to false) when
> deciding not to show the textual diff.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> * Strictly speaking any change is backward incompatible, and this is
> certainly one, but I do not think of a good use case to depend on the
> previous behaviour, which was reported as a bug by my coworker.
I'm not sure this is a good idea. In our repository, for example, we
have a few files that are strictly speaking "text" but absolutely,
positively must be CRLF on all platforms because the idiotic
proprietary parsers and generators that manipulate them need it to be
that way.
I think the bug is that "crlf=false" should not be considered the same
as "binary=true", which seems to be a bug in the documentation, not
the program.
Have fun,
Avery
next prev parent reply other threads:[~2008-08-29 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 21:28 [PATCH] diff: treat -crlf files as binary Junio C Hamano
2008-08-29 21:56 ` Avery Pennarun [this message]
2008-08-30 21:34 ` Junio C Hamano
2008-08-31 2:34 ` Avery Pennarun
2008-08-31 8:27 ` Matthieu Moy
2008-08-31 9:16 ` Alex Riesen
2008-08-31 16:25 ` Junio C Hamano
2008-08-31 18:34 ` Avery Pennarun
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=32541b130808291456k3de953a2yd1e93bc27ad14293@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).