git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: [RFC] gitk using diff-tree -M for merges
Date: Fri, 11 May 2007 10:45:56 +0200	[thread overview]
Message-ID: <20070511084556.GB5485@informatik.uni-freiburg.de> (raw)

Hello,

looking at the diff that commit 070739fd351702ea9bb4f65595728ae25a488075
introduced with gitk from 1.5.2-rc3 [1], I'd prefer gitk using the
option -M for diff-tree to detect that in 3f28f63f git-gui.sh exists,
too.  Currently the diff is a bit longer that the whole file, with -M it
would be empty.

Probably using -M hurts performance, so it should better be a config
option?

Below is a patch that hardcodes -M, I didn't check if there are more
places where it should be added.

What do you think?

Best regards
Uwe

[1] the following is a nice view:

	gitk 070739fd351702ea9bb4f65595728ae25a488075 ^53a58245863eff3d70aaa3ac75d7d57e843fc91d^ ^e701ccc3883959b4ba5fada7a903e8e9eaddcba7

diff --git a/gitk b/gitk
index a57e84c..bcc4637 100755
--- a/gitk
+++ b/gitk
@@ -4240,7 +4240,7 @@ proc mergediff {id l} {
     set diffids $id
     # this doesn't seem to actually affect anything...
     set env(GIT_DIFF_OPTS) $diffopts
-    set cmd [concat | git diff-tree --no-commit-id --cc $id]
+    set cmd [concat | git diff-tree -M --no-commit-id --cc $id]
     if {[catch {set mdf [open $cmd r]} err]} {
 	error_popup "Error getting merge diffs: $err"
 	return

-- 
Uwe Kleine-König

http://www.google.com/search?q=1+electron+mass%3D

                 reply	other threads:[~2007-05-11  8:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070511084556.GB5485@informatik.uni-freiburg.de \
    --to=ukleinek@informatik.uni-freiburg.de \
    --cc=git@vger.kernel.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 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).