From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
"Clemens Buchacher" <drizzd@aon.at>,
"Clément Poulain" <clement.poulain@ensimag.imag.fr>,
"Diane Gasselin" <diane.gasselin@ensimag.imag.fr>,
"Axel Bonnet" <axel.bonnet@ensimag.imag.fr>
Subject: Re: [PATCH] git-gui: use textconv filter for diff and blame
Date: Fri, 30 Jul 2010 08:56:37 +0200 [thread overview]
Message-ID: <vpq8w4tpie2.fsf@bauges.imag.fr> (raw)
In-Reply-To: <871valstsi.fsf@fox.patthoyts.tk> (Pat Thoyts's message of "Fri\, 30 Jul 2010 01\:22\:05 +0100")
Pat Thoyts <patthoyts@users.sourceforge.net> writes:
> This looks generally fine but can you suggest some test that I can use
> to ensure it is actually doing something. I tried committing some test
> files containing cyrillic characters but I see no difference between
> using an unpatched git-gui and your patched version with git 1.7.2
textconv has not much to do with encoding. It's a way to tell git the
name of a command that converts a file into plain text. Typical usages
would be to use odt2txt, catdoc/antiword, or meta-information
extraction (like exiftags).
Have a look here:
https://git.wiki.kernel.org/index.php/Textconv
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-07-30 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 12:23 [PATCH] git-gui: use textconv filter for diff and blame Matthieu Moy
2010-07-30 0:22 ` Pat Thoyts
2010-07-30 6:56 ` Matthieu Moy [this message]
2010-07-30 10:30 ` Pat Thoyts
2010-07-30 10:40 ` Matthieu Moy
2010-08-02 19:01 ` Junio C Hamano
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=vpq8w4tpie2.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=axel.bonnet@ensimag.imag.fr \
--cc=clement.poulain@ensimag.imag.fr \
--cc=diane.gasselin@ensimag.imag.fr \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
--cc=spearce@spearce.org \
/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.