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 12:12:48 -0500 [thread overview]
Message-ID: <20101022171248.GA11794@burratino> (raw)
In-Reply-To: <1287766916.31218.71.camel@drew-northup.unet.maine.edu>
Hi again,
Drew Northup wrote:
> That still doesn't fix the crlf issue, for starters. Also, I would like
> to be able to email patches for files that are in UTF-16 and properly
> re-import them. Unless I'm missing something really big there's not much
> that a display filter is going to do for me there.
Right, I think you're missing something big. textconv is a display
filter. clean/smudge convert between internal and external
representation (and your clean/smudge scripts could take care of CRLF
themselves if desired).
That said, I wouldn't be surprised if clean/smudge filters don't do
everything you want. If you do go that way, please keep the list
posted so the mechanism can be improved.
And longer term, maybe people will want something tailor-made after
all? I just imagine it would be more productive to try out the
generic mechanisms first.
next prev parent reply other threads:[~2010-10-22 17:16 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
2010-10-22 17:01 ` Drew Northup
2010-10-22 17:12 ` Jonathan Nieder [this message]
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=20101022171248.GA11794@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 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).