On Thursday, March 24, 2016 at 10:10:30 AM UTC-7, Justin Dolske wrote:
> On 3/24/16 9:54 AM, Ralph Giles wrote:
> > On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote:
> >
> >> tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
> >> worry about backward compatibility tho, wh
On 3/24/16 9:54 AM, Ralph Giles wrote:
On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote:
tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
worry about backward compatibility tho, when MOZ_LOG_* is not set, we
fallback to NSPR_LOG_* values.
Could this be an opportuni
On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote:
> tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
> worry about backward compatibility tho, when MOZ_LOG_* is not set, we
> fallback to NSPR_LOG_* values.
Could this be an opportunity to shorten NSPR_LOG_MODULES to jus
On 3/21/2016 18:17, Nicholas Alexander wrote:
On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote:
tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
worry about backward compatibility tho, when MOZ_LOG_* is not set, we
fallback to NSPR_LOG_* values.
Hi Honza,
Thanks f
On Mon, Mar 21, 2016 at 9:13 AM, Honza Bambas wrote:
> tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
> worry about backward compatibility tho, when MOZ_LOG_* is not set, we
> fallback to NSPR_LOG_* values.
>
Hi Honza,
Thanks for making the world a better place! I'm s
tl;dr: Start migrating to use of MOZ_LOG_* instead of NSPR_LOG_*. Don't
worry about backward compatibility tho, when MOZ_LOG_* is not set, we
fallback to NSPR_LOG_* values.
The longer version:
Since the new logging code sits in XPCOM and has no longer anything to
do with NSPR and NSPR loggi
6 matches
Mail list logo