Re: git-kompare

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Aug 24, 2007, 19:52 UTC
Message-ID: <200708242152.09176.robin.rosenberg.lists@dewire.com>
In-Reply-To: <200708241813.48012.andyparkins@gmail.com>

fredag 24 augusti 2007 skrev Andy Parkins:

Show 8 quoted lines

> 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