From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, Jean-Marc Valin <jean-marc.valin@csiro.au>
Subject: Re: git-kompare
Date: Fri, 24 Aug 2007 21:52:08 +0200 [thread overview]
Message-ID: <200708242152.09176.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <200708241813.48012.andyparkins@gmail.com>
fredag 24 augusti 2007 skrev Andy Parkins:
> On Friday 2007, August 24, Jean-Marc Valin wrote:
>
> > (http://mail.kde.org/pipermail/kompare-devel/2006-August/000141.html
> > which is fixed in some later version of kompare I think)
>
> I was the original reporter of that bug; I have to say the kompare
> developers were fairly quick on the uptake and fixed that problem with the
> next realease of kompare - which came very soon after the report. I just
I am more of a GIT developer than a KDE developer.
> waited for it to arrive in debian unstable, which also happened fairly
> quickly. If you are seriously that far behind in your kompare version I
> strongly suggest upgrading, I mean, if it's in debian then it's in
> everything else :-)
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.
> I found it quite nostalgic seeing that report, as I made the report a few
> days after my first use of git, which means I've just had my git
> anniversary. How quickly time flys - I can hardly believe I ever managed
> without it now.
This was about two months after starting to use git in my case. My first git bug was
encountered abour ten minutes after trying git. (Linus fixed the bug the day after).
-- robin
next prev parent reply other threads:[~2007-08-24 19:51 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 ` Robin Rosenberg [this message]
2007-08-25 0:17 ` git-kompare Jean-Marc Valin
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=200708242152.09176.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jean-marc.valin@csiro.au \
/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).