Sorry - I wasn't subscribed to the bug, but a user just emailed me with a
bug report today, so I got back into checking it out.
I am still interested in the project, and I have been thinking that I
should get back to it, but I was thinking maybe I was the only one using
it, but I see a couple bug reports, so it would be worth getting my code
published, and get the one other patch included (I have noticed the CPU
usage issue to, but never looked into it).
I had published the changes with how I thought it was supposed to be, but
I made some sort of mistake, and had some paths wrong in the diff files,
so it showed some things from my development machine, so I removed the
upload.
I'll take another look at it this week and see if I can get the proper
diffs generated. I don't think I have my changes marked as public, but I
can definitely do that this week, even if I can't figure out how to build
it properly for debian.
--
Jon Daley
http://jon.limedaley.com
~~
Normal people believe that if it ain't broke,
don't fix it.
Engineers believe that if it ain't broke,
it doesn't have enough features yet.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
