From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Al Haraka <alharaka@gmail.com>,
git@vger.kernel.org
Subject: [PATCH] docs: document --textconv diff option
Date: Wed, 6 Jul 2011 11:13:30 -0400 [thread overview]
Message-ID: <20110706151330.GA13790@sigill.intra.peff.net> (raw)
In-Reply-To: <m3r5634ijc.fsf@localhost.localdomain>
On Wed, Jul 06, 2011 at 06:59:53AM -0700, Jakub Narebski wrote:
> Actually I think neither git-format-patch (which is used by 'patch'
> and 'patches' views), not git-diff-tree (used by 'commitdiff' and
> 'blobdiff' views, and their *_plain versions) supports --textconv,
> and that it is supported only by git-diff. But you better check that.
I did. It works for both.
> Nb documentation as of 1.7.5 is entirely unhelpful. Only git-cat-file
> is documented as using --textconv... though this option is examined
> in diff.c, and there is test for git-blame supporting it.
Patch below.
> By the way, I don't know if git read .gitattributes file (which
> defines textconv... unless you use per repository instance
> .git/info/attributes) from tree for given commit, or only from working
> area.
It's not currently read from the tree; see earlier in the thread for
some discussion.
-Peff
-- >8 --
Subject: [PATCH] docs: document --textconv diff option
This has been there since textconv existed, but was never
documented. There is some overlap with what's in
gitattributes(5), but it's important to warn in both places
that textconv diffs probably can't be applied.
Signed-off-by: Jeff King <peff@peff.net>
---
Documentation/diff-options.txt | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
index 4235302..b620b3a 100644
--- a/Documentation/diff-options.txt
+++ b/Documentation/diff-options.txt
@@ -422,6 +422,17 @@ endif::git-format-patch[]
--no-ext-diff::
Disallow external diff drivers.
+--textconv::
+--no-textconv::
+ Allow (or disallow) external text conversion filters to be run
+ when comparing binary files. See linkgit:gitattributes[5] for
+ details. Because textconv filters are typically a one-way
+ conversion, the resulting diff is suitable for human
+ consumption, but cannot be applied. For this reason, textconv
+ filters are enabled by default only for linkgit:git-diff[1] and
+ linkgit:git-log[1], but not for linkgit:git-format-patch[1] or
+ diff plumbing commands.
+
--ignore-submodules[=<when>]::
Ignore changes to submodules in the diff generation. <when> can be
either "none", "untracked", "dirty" or "all", which is the default
--
1.7.6.20.g45f3f.dirty
prev parent reply other threads:[~2011-07-06 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 9:50 Gitweb 1.7.5 and Textconv Configuration Al Haraka
2011-07-02 10:43 ` Jeff King
2011-07-02 10:44 ` Jeff King
2011-07-02 11:14 ` Al Haraka
2011-07-02 18:57 ` Jeff King
2011-07-02 19:18 ` Al Haraka
2011-07-02 19:57 ` Jeff King
2011-07-02 20:23 ` Jakub Narebski
2011-07-02 21:10 ` Jeff King
2011-07-02 21:22 ` Jakub Narebski
2011-07-02 21:10 ` Al Haraka
2011-07-06 13:59 ` Jakub Narebski
2011-07-06 15:13 ` Jeff King [this message]
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=20110706151330.GA13790@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=alharaka@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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).