--On Friday, March 25, 2005 9:39 AM -0800 Michael Vogt <[EMAIL PROTECTED]> wrote:
I'll have to take a look at that latest version.
How should I have known about these problems prior to noticing them myself? I did not see them in the sourcefurge bug tracking. Where else should I look before reporting problems?
Thanks for all your contributions to mon,
Sorry, there wasn't really any way for you to know about this. These were probably bugs which I discovered much like you did, and fixed in my local Mon copy. I don't know offhand whether they were in the patches that I sent to Jim back before we started working together directly, but those patches never got integrated anyway.
When Jim agreed to collaborate on further Mon development we re-activated what had been essentially a dead sourceforge project and I basically integrated all of my outstanding changes at once, carefully reading through all the changes at the time to make sure I wasn't breaking anything. I also went through and essentially cleared out the pending sourceforge bug queue at the time, because it hadn't been monitored or updated in a long time.
-David
David Nolan <*> [EMAIL PROTECTED] curses: May you be forced to grep the termcap of an unclean yacc while a herd of rogue emacs fsck your troff and vgrind your pathalias!
_______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon