[Asterisk-code-review] backtrace: Avoid potential spurious output. (asterisk[master])
Alexander Traud
asteriskteam at digium.com
Sat Feb 10 07:55:48 CST 2018
Hello Richard Mudgett, Jenkins2,
I'd like you to reexamine a change. Please visit
https://gerrit.asterisk.org/8104
to look at the new patch set (#2).
Change subject: backtrace: Avoid potential spurious output.
......................................................................
backtrace: Avoid potential spurious output.
clang 4.0 found this via -Wlogical-not-parentheses.
ASTERISK-27642
Change-Id: I9ec3e144d425a976c02811bd23cd0c533d2eca4e
---
M main/backtrace.c
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.asterisk.org:29418/asterisk refs/changes/04/8104/2
--
To view, visit https://gerrit.asterisk.org/8104
To unsubscribe, visit https://gerrit.asterisk.org/settings
Gerrit-Project: asterisk
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I9ec3e144d425a976c02811bd23cd0c533d2eca4e
Gerrit-Change-Number: 8104
Gerrit-PatchSet: 2
Gerrit-Owner: Alexander Traud <pabstraud at compuserve.com>
Gerrit-Reviewer: Alexander Traud <pabstraud at compuserve.com>
Gerrit-Reviewer: Jenkins2
Gerrit-Reviewer: Richard Mudgett <rmudgett at digium.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-code-review/attachments/20180210/79a9d4c9/attachment.html>
More information about the asterisk-code-review
mailing list