Re: how to test out cron.c changes? (was: cvs commit: src/etccrontab)

2001-01-22 Thread Sergey Babkin
Greg Black wrote: Sergey Babkin wrote: It still can be backed out. Well, what are you waiting for? Back it out. Listen to what people are saying and then maybe propose something that takes into account their concerns. I wanted to get a confirmation from Doug Barton that he still

Re: how to test out cron.c changes? (was: cvs commit: src/etccrontab)

2001-01-21 Thread Dan Langille
Sergy wrote: As far as I've watched this thread nobody had explained it. So could you please elaborate ? Nobody explained it to your satisfaction but you still committed it? Nobody explained it to my satisfaction why I should not commit it. Ummm, well, that's a good reason to

Re: how to test out cron.c changes? (was: cvs commit: src/etccrontab)

2001-01-21 Thread Sergey Babkin
Dan Langille wrote: On 21 Jan 2001, at 14:50, Sergey Babkin wrote: Let me ask a simple question: Why ? What are the benefits of preserving the old behavior ? First, it's not "old" behaviour. It is existing behaviour. There is a difference. Because that's what was discussed and

Re: how to test out cron.c changes? (was: cvs commit: src/etccrontab)

2001-01-21 Thread Greg Black
Sergey Babkin wrote: It still can be backed out. Well, what are you waiting for? Back it out. Listen to what people are saying and then maybe propose something that takes into account their concerns. To make this point a little more clearly -- the fact that Matt Dillon, who is no fool, and