From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Lars Schneider <larsxschneider@gmail.com>,
Steve Groeger <GROEGES@uk.ibm.com>,
git@vger.kernel.org
Subject: Re: Use of new .gitattributes working-tree-encoding attribute across different platform types
Date: Tue, 03 Jul 2018 09:01:05 -0700 [thread overview]
Message-ID: <xmqqsh50s3zy.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180702181742.GA12208@sigill.intra.peff.net> (Jeff King's message of "Mon, 2 Jul 2018 14:17:42 -0400")
Jeff King <peff@peff.net> writes:
> One thing I almost did in the example I gave above was to literally call
> the encoding name by a "real" one. I.e.:
>
> echo '*.txt working-tree-encoding=iso-8859-1' >.gitattributes
> git config encoding.iso-8859-1.replace latin1
>
> or something. But I wondered if it was a little crazy as a practice,
> since mapping "iso-8859-1" to "utf-8" is probably going to lead to
> headaches.
>
> But your example above of semantically equivalent variants with
> different spellings would be a good use of that trick.
Yeah, I think the above looks quite sensible.
next prev parent reply other threads:[~2018-07-03 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 7:54 Use of new .gitattributes working-tree-encoding attribute across different platform types Steve Groeger
2018-06-27 17:38 ` Torsten Bögershausen
2018-06-28 2:44 ` brian m. carlson
2018-06-28 14:34 ` Jeff King
2018-06-28 17:21 ` Lars Schneider
2018-06-28 17:27 ` Jeff King
2018-07-01 17:56 ` brian m. carlson
2018-07-02 18:17 ` Jeff King
2018-07-03 16:01 ` Junio C Hamano [this message]
2018-07-02 12:13 ` Steve Groeger
2018-07-02 14:09 ` Lars Schneider
2018-07-02 18:20 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2018-06-27 7:50 Steve Groeger
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=xmqqsh50s3zy.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=GROEGES@uk.ibm.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).