[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50658: Error messages including function names violates coding conve
From: |
Eli Zaretskii |
Subject: |
bug#50658: Error messages including function names violates coding conventions |
Date: |
Sat, 18 Sep 2021 16:25:32 +0300 |
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 18 Sep 2021 05:49:37 -0700
> Cc: 50658@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks. If we are going to show examples (which is a good idea, IMO),
> > I think we should show both examples with and without the function
> > name, and therefore some wording about the function name being
> > optional, and that the rule is not applicable to it, is in order.
>
> OK, that makes sense. What do you think of this:
LGTM, thanks.
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/27
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28