From: Junio C Hamano <gitster@pobox.com>
To: Chris Harris <ryguasu@gmail.com>
Cc: Jeff King <peff@peff.net>, Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: Is the "text" attribute meant *only* to specify end-of-line normalization behavior, or does it have broader implications?
Date: Fri, 30 Mar 2012 11:22:06 -0700 [thread overview]
Message-ID: <7v62dmlzjl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CANSc5vGaodyv4H5qp2ZkjY7q6ot7_JG0jdvNDFRBFW1+p7v4sw@mail.gmail.com> (Chris Harris's message of "Fri, 30 Mar 2012 10:49:42 -0700")
Chris Harris <ryguasu@gmail.com> writes:
> A related point of confusion: I've noticed that, if you start with a
> question along the lines of "how can I explicitly tell git that a file
> is binary", then the web currently gives a slightly confusing array of
> answers. For example:
>...
> It makes me wonder if the documentation could be improved a little on
> this count, though I don't yet feel solid enough in my understanding
> to propose a particular patch.
If you only read your analysis on gitattributes documentation, it would be
clear that text/-text does not have much to do with binaryness, and it
also gives an authoritative advice "binary".
We do not have direct control over third-party sites that give incorrect
information, so people need to bug them as they find mistakes. I think
ProGit actively accepts patches; I do not know about others.
Thanks.
next prev parent reply other threads:[~2012-03-30 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 2:19 Is the "text" attribute meant *only* to specify end-of-line normalization behavior, or does it have broader implications? Chris Harris
2012-03-30 6:42 ` Johannes Sixt
2012-03-30 7:25 ` Jeff King
2012-03-30 17:49 ` Chris Harris
2012-03-30 18:22 ` Junio C Hamano [this message]
2012-03-30 21:30 ` Jeff King
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=7v62dmlzjl.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.net \
--cc=ryguasu@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).