Summary: | outdated and conflicting code (timidity) | ||
---|---|---|---|
Product: | [Unmaintained] kmidi | Reporter: | David Walser <luigiwalser> |
Component: | general | Assignee: | Russell Miller <rmiller> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | esigra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David Walser
2003-05-26 17:25:14 UTC
I can believe this. So I'm accepting the bug. One possible resolution to this bug would be to find a way to scrape together the kmidi GUI code and get it into a form where it could be submitted to TiMidity++, which already has hooks in place for such code. The hardest things would be distinguishing that code from the rest of the crap in the kmidi directory, and reworking it to hook it into current TiMidity++. Subject: Re: outdated and conflicting code (timidity)
On Thu, Jul 03, 2003 at 05:50:53PM -0000, David Walser wrote:
>
> ------- Additional Comments From luigiwalser@yahoo.com 2003-07-03 19:50 -------
> One possible resolution to this bug would be to find a way to scrape together the kmidi
> GUI code and get it into a form where it could be submitted to TiMidity++, which
> already has hooks in place for such code.
>
> The hardest things would be distinguishing that code from the rest of the crap in the
> kmidi directory, and reworking it to hook it into current TiMidity++.
It's not a bad idea, but I think I will hold off on that until I have a
better idea of what's needed.
--Russell
Bug #39574 will be resolved by the same action that will resolve this bug, and because of that, both bugs are equally critical. So I am marking this bug as a duplicate. Please track #39574 if you wish to follow progress further. *** This bug has been marked as a duplicate of 39574 *** |