From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: kompare won't parse git diffs
Date: Wed, 2 Aug 2006 11:07:39 +0100 [thread overview]
Message-ID: <200608021107.43485.andyparkins@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hello,
Kompare just shows blank for diffs redirected from git. This makes it
I've tracked down the cause and it seems to be on the file declaration lines.
Here is a sample diff that kompare will not show.
diff --git a/file b/file
index a8b2ec6..a1e65fd 100644
--- a/file
+++ b/file
@@ -1,2 +1,3 @@
initial contents goes in master branch
additional content added in repo1#master
+blah
As you can see, it's a simple addition of the line "blah". Kompare shows this
diff as blank. Now if I modify the file so that the "---" and "+++" lines
both have "<tab>(something)" added:
diff --git a/file b/file
index a8b2ec6..a1e65fd 100644
--- a/file (anything can go here)
+++ b/file (anything can go here)
@@ -1,2 +1,3 @@
initial contents goes in master branch
additional content added in repo1#master
+blah
http://bugs.kde.org/show_bug.cgi?id=131717
I've posted a bug for kompare, but thought that maybe it would be handy if git
outputted those bracketed comments anyway - I notice that "diff -u" from the
command line does (although it uses the timestamp of the file). Maybe the
object hash of the files being compared could go here?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-08-02 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 10:07 Andy Parkins [this message]
2006-08-02 17:19 ` kompare won't parse git diffs Linus Torvalds
2006-08-02 18:12 ` Jakub Narebski
2006-08-02 19:17 ` Junio C Hamano
2006-08-06 3:14 ` Paul Eggert
2006-08-02 19:19 ` Linus Torvalds
2006-08-02 20:18 ` Jakub Narebski
2006-08-02 20:51 ` Linus Torvalds
2006-08-02 18:18 ` Andy Parkins
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=200608021107.43485.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--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 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.