From: Jonathan Nieder <jrnieder@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC] Print diffs of UTF-16 to console / patches to email as UTF-8...?
Date: Fri, 22 Oct 2010 11:18:51 -0500 [thread overview]
Message-ID: <20101022161851.GH9224@burratino> (raw)
In-Reply-To: <1287763608.31218.63.camel@drew-northup.unet.maine.edu>
Hi,
Drew Northup wrote:
> This is part of my ongoing work to treat UTF-16 as text (in
> other words, the crlf options will work and .gitattributes hacks won't
> be required to display diffs, etc).
What's wrong with .gitattributes for this use case? I would think a
clean/smudge filter would produce very good behavior from most git
commands.
If speed is the issue, maybe a built-in clean/smudge filter would
address that?
next prev parent reply other threads:[~2010-10-22 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 16:06 [RFC] Print diffs of UTF-16 to console / patches to email as UTF-8...? Drew Northup
2010-10-22 16:18 ` Jonathan Nieder [this message]
2010-10-22 17:01 ` Drew Northup
2010-10-22 17:12 ` Jonathan Nieder
2010-10-22 17:27 ` Drew Northup
2010-10-22 17:30 ` Jonathan Nieder
2010-10-22 17:58 ` Jakub Narebski
2010-10-22 17:48 ` Jakub Narebski
2010-10-22 18:06 ` Drew Northup
2010-10-22 19:18 ` Jakub Narebski
2010-10-22 18:28 ` Joshua Juran
2010-10-22 19:13 ` Jeff King
2010-10-22 19:53 ` Jonathan Nieder
2010-10-22 20:18 ` Git Attribute: File Text Encoding {WAS: Re: [RFC] Print diffs of UTF-16 to console / patches to email as UTF-8...?} Drew Northup
2010-10-22 21:49 ` Jakub Narebski
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=20101022161851.GH9224@burratino \
--to=jrnieder@gmail.com \
--cc=drew.northup@maine.edu \
--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 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.