This is the first patch of the series. The first two patches are improvements of the log output and are independent of the 3rd patch in terms of code - proposed logging improvements just make it easier to debug issues with MNCC cause codes.
The code is also a part of the achemeris/mncc_cause_fixes_master branch.
bump
It doesn't seem there are any comments on this set of patches. Is it ok to merge them?
On Sun, Sep 13, 2015 at 3:46 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
This is the first patch of the series. The first two patches are improvements of the log output and are independent of the 3rd patch in terms of code - proposed logging improvements just make it easier to debug issues with MNCC cause codes.
The code is also a part of the achemeris/mncc_cause_fixes_master branch.
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
On 24 Nov 2015, at 02:01, Alexander Chemeris alexander.chemeris@gmail.com wrote:
Dear Alexander,
bump
It doesn't seem there are any comments on this set of patches. Is it ok to merge them?
the reason is simple and stupid at the same time. I look for pending patches in patchwork and patchwork does not find/see patches that are attachments to mail. If you could, please re-send them inline or try to use git send-email.
kind regards holger
On Wed, Nov 25, 2015 at 11:08 PM, Holger Freyther holger@freyther.de wrote:
On 24 Nov 2015, at 02:01, Alexander Chemeris alexander.chemeris@gmail.com wrote: bump
It doesn't seem there are any comments on this set of patches. Is it ok to merge them?
the reason is simple and stupid at the same time. I look for pending patches in patchwork and patchwork does not find/see patches that are attachments to mail.
Weird.
If you could, please re-send them inline or try to use git send-email.
Let me try
-
Alexander Chemeris -
Holger Freyther