Gerhard Sittig wrote: > > [ ... reminder after two weeks of silence ... ] Two weeks of silence is generally enough to let you know that no one is interested in this modification. If someone was, they'd generally have said something by now. Speaking only for myself, I don't think your proposed changes are a good idea, which is why I refrained from offering any suggestions on how you can test them. Just so you wouldn't think you were being ignored, Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: how to test out cron.c changes? (was: cvs commit: s... Gerhard Sittig
- Re: how to test out cron.c changes? (was: cvs comm... Gerhard Sittig
- Re: OT: silence as an answer? (was: how to tes... Doug Barton
- Re: OT: silence as an answer? (was: how to... Gerhard Sittig
- Re: OT: silence as an answer? (was: ho... Neil Blakey-Milner
- Re: OT: silence as an answer? (was: ho... Dan Langille
- Re: OT: silence as an answer? (was: ho... Doug Barton
- Re: OT: silence as an answer? (wa... Gordon Tetlow
- Re: OT: silence as an answer?... Doug Barton
- Re: OT: silence as an answer? (wa... Gerhard Sittig
- Re: how to test out cron.c changes? (was: ... Gerhard Sittig
- Re: how to test out cron.c changes? (w... John Baldwin
- Re: how to test out cron.c change... Gerhard Sittig