From: Jean-Marc Valin <jean-marc.valin@csiro.au>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: git-kompare
Date: Sat, 25 Aug 2007 10:17:13 +1000 [thread overview]
Message-ID: <46CF7509.5080206@csiro.au> (raw)
In-Reply-To: <200708242152.09176.robin.rosenberg.lists@dewire.com>
> Adding the patch to your version isn't hard. Just download the source package
> and add the patch in the patches section and rebuild. That's how I lived with
> the fix until Mandriva delivered a newer KDE version. Thanks to the kdesdk src
> rpm I could rebuild the package fairly easily without dowloading, configuring
> and builing most of KDE. The src rpm declare the dependencies I need. My
> guess is that is about as easy with dpkg, ebuilds or ports.
Unless I missed something, there are more things to work around than the
one that was fixed in your patch, no? For example, the fact that kompare
doesn't understand when the filename is /dev/null. As for upgrading
kompare, I'm all for the idea, but the KDE folks aren't making that
easy. The only link in the Kompare download section is for www.kde.org,
which isn't making the source code any easier to find (including a 404
link for "Source code" on the front page!). Any direct link?
BTW, I'm running the latest Ubuntu (Feisty) that ships with kompare 3.4.
Jean-Marc
next prev parent reply other threads:[~2007-08-25 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 5:40 git-kompare Jean-Marc Valin
2007-08-24 17:13 ` git-kompare Andy Parkins
2007-08-24 19:52 ` git-kompare Robin Rosenberg
2007-08-25 0:17 ` Jean-Marc Valin [this message]
2007-08-25 10:25 ` git-kompare Robin Rosenberg
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=46CF7509.5080206@csiro.au \
--to=jean-marc.valin@csiro.au \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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 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.