https://fedorapeople.org/groups/389ds/ci/nightly/2019/05/16/report-389-ds-base-1.4.1.2-20190515git41c30fd.fc29.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
Replying to both Simon and Ludwig in the one mail ...
To just comment to one point from Ludwig:
> This may sound too negative, I agree that logging deserves attention and
> improvement, but we need to agree on what we want to achieve.
I don't think this is negative, at all and I think it's
Hi
I will also help from QA team(Test and automation ) , i started learning
"rust" 6 month ago (not regular ). I know 2% (may be).
Regards
Anuj Borah
On Wed, May 15, 2019 at 8:20 PM Simon Pichugin wrote:
> On Tue, May 14, 2019 at 01:21:28PM +1000, William Brown wrote:
> > Hi all,
> >
> > So
On Tue, May 14, 2019 at 01:21:28PM +1000, William Brown wrote:
> Hi all,
>
> So it's been a while since I pushed this, but again, I think I want to bring
> this up. I'd like to write the new logging backend in Rust.
>
> I'll start with a summary:
>
> Pros:
> * Faster development time due to
Hi William,
this is a good starting point to discuss and decide how to move forward
with logging (although it looks like you are already some steps ahead).
I have no strong ties to existing logging format and if we do it in rust
or not I don't care, but I do not want to use existing
