-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Pádraig Brady on 12/1/2008 10:15 AM:
> Bo Borgerson wrote:
>> Pádraig Brady wrote:
>>> p.s. Those new --check-order --nocheck-order options confuse me.
>>> When they were added I only took a quick look at the implementation
>>> rather than the interface (which Bo Borgerson kindly sped up for us).
>>> Perhaps something like this would be clearer:
>>>
>>> --check-order={none,mismatch,unsorted}
>>> By default --check-order=mismatch is enabled.
I like that proposal.
>> but it should be possible to allow both:
>>
>> --nocheck-order => --check-order=none
>> [DEFAULT] => --check-order=warning
>> --check-order => --check-order=fatal
>
> If we were going to change it I would not support both.
> I.E. I would not support the --nocheck-order option.
> I guess very few scripts actually use the --nocheck-order option.
I could go either way, but agree that --nocheck-order is probably a
new-enough invention that we can remove it altogether.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkk0RMcACgkQ84KuGfSFAYBaTQCeM+m6Jz33BdzDXoNnCdEipZpe
jPUAmQFSs5D7aVtwu0vK0hVeUDVrWxq2
=e4FZ
-----END PGP SIGNATURE-----
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
