-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Originally, we planned to deprecate the decimal values for the debug levels, but that has proven to be too difficult for most users to understand. Instead, we will document both the simple decimal and complex bitmask values and recommend the use of the decimal values.
On Mon, Oct 07, 2013 at 09:19:14AM -0400, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Originally, we planned to deprecate the decimal values for the debug levels, but that has proven to be too difficult for most users to understand. Instead, we will document both the simple decimal and complex bitmask values and recommend the use of the decimal values.
Thank you, the user who recently reported a Fedora bug was confused by having to AND the values. Plus, the hexadecimal values never really caught up aside from developers.
The patches build find, the resulting man page reads well to me.
ACK
On Mon, Oct 07, 2013 at 03:42:54PM +0200, Jakub Hrozek wrote:
On Mon, Oct 07, 2013 at 09:19:14AM -0400, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Originally, we planned to deprecate the decimal values for the debug levels, but that has proven to be too difficult for most users to understand. Instead, we will document both the simple decimal and complex bitmask values and recommend the use of the decimal values.
Thank you, the user who recently reported a Fedora bug was confused by having to AND the values. Plus, the hexadecimal values never really caught up aside from developers.
The patches build find, the resulting man page reads well to me.
ACK
Pushed both patches to master and sssd-1-11
On 10/07/2013 03:42 PM, Jakub Hrozek wrote:
On Mon, Oct 07, 2013 at 09:19:14AM -0400, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Originally, we planned to deprecate the decimal values for the debug levels, but that has proven to be too difficult for most users to understand. Instead, we will document both the simple decimal and complex bitmask values and recommend the use of the decimal values.
Thank you, the user who recently reported a Fedora bug was confused by having to AND the values. Plus, the hexadecimal values never really caught up aside from developers.
I personally use only 0x0ff0 and switch to 0x[13]ff0 when needed. To make better use of it we would have to create more levels and refactor all existing debug messages. From the top of my had we could split TRACE_ALL to separate info messages (like sudo rules names) and ldb messages.
The patches build find, the resulting man page reads well to me.
ACK
sssd-devel@lists.fedorahosted.org