New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup lib389 log messages around commands #1810
Comments
Comment from firstyear (@Firstyear) at 2016-03-02 14:30:14 attachment |
Comment from spichugi (@droideck) at 2016-03-04 23:01:38 Hi William, I think it is great that you've decided to clean up our logs. But, unfortunately, a lot of lib389 tests fail with your patch. Can you please fix tests too and include changes to your patch? Just be sure that all of them are still pass. :) Thanks, |
Comment from firstyear (@Firstyear) at 2016-03-08 09:10:44 Reinstate product name |
Comment from firstyear (@Firstyear) at 2016-03-08 09:11:10 Hi, I didn't find anywhere that used it, which is why I removed it. I've put it back now. Sorry about the confusion. |
Comment from spichugi (@droideck) at 2016-03-08 18:12:42 Thanks, all tests PASS. Looks good to me. Ack. |
Comment from firstyear (@Firstyear) at 2016-03-09 05:49:41 commit d33624108669bafa12acd46b4544fee329933fda |
Comment from spichugi (@droideck) at 2017-02-11 22:51:29 Metadata Update from @droideck:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48750
Clean up the lib389 log messages around commands so that it's a cleaner user experience.
The text was updated successfully, but these errors were encountered: