David Boyce wrote: > I'm unsurprised at seeing no public response to > yours either. But disappointed.
I'm not disappointed. Paul doesn't work for me so there is no obligation for him to write patches or design specs supporting my use cases. And neverthless, so far I've had no reason to be unhappy with what he does. > I think the best approach is probably to follow the CVS commit trail, > find the commit which fixed the original bug, and Yes, that's probably good advice. Cheers, Jonathan _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
