--- Comment #7 from Per Jessen <per(a)opensuse.org> 2012-09-14 19:23:17 UTC ---
(In reply to comment #6)
(In reply to comment #2)
It's just taken us a little long to find
And this might be a problem in itsself ;-) In this case the question is:
Does "fixing" this bug cause more harm than good?
Don't get me wrong - in general, I'm all for fixing bugs - but in this case,
how many log-analysis scripts etc. (which expect uppercase CRON in the
meantime) will we break?
It's a good question, but if we assume that the same amount of new scripts are
written per release, it's easily answered:
lowercase cron output in releases 7.x/8.x/9.x/10.x/11.x
uppercase cron output in releases 11.4,12.1
There's no way of really answering the question, but probabilistically
speaking, the change to uppercase in 11.4 broke more scripts than a change back
now will break. 12.1 and 12.2 have not yet been put into production in many
I think we should revert to lowercase, using the same argument that was applied
whenever it was changed to lowercase.
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.