From: "Måns Rullgård" <mans@mansr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] GCC 7.x vs. C++ comments
Date: Thu, 10 May 2018 13:07:20 +0100 [thread overview]
Message-ID: <yw1xa7t7af47.fsf@mansr.com> (raw)
In-Reply-To: <20180509134905.GK12235@bill-the-cat.ec.rr.com> (Tom Rini's message of "Wed, 9 May 2018 09:49:05 -0400")
Tom Rini <trini@konsulko.com> writes:
> - Shorter
Please explain how
// SPDX
is significantly shorter than
/* SPDX */
Having // comments next to /* ones is just hideously ugly. If some
scanning tool is too stupid to handle standard C comments, it's the tool
that needs to be fixed.
--
Måns Rullgård
prev parent reply other threads:[~2018-05-10 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 8:46 [U-Boot] GCC 7.x vs. C++ comments Dr. Philipp Tomsich
2018-05-09 11:16 ` Tom Rini
2018-05-09 11:38 ` Wolfgang Denk
2018-05-09 11:48 ` Tom Rini
2018-05-09 12:46 ` Wolfgang Denk
2018-05-09 13:49 ` Tom Rini
2018-05-09 14:11 ` Dr. Philipp Tomsich
2018-05-09 15:40 ` Wolfgang Denk
2018-05-09 16:07 ` Wolfgang Denk
2018-05-09 16:22 ` Tom Rini
2018-05-09 16:14 ` Tom Rini
2018-05-09 20:44 ` Wolfgang Denk
2018-05-10 12:07 ` Måns Rullgård [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xa7t7af47.fsf@mansr.com \
--to=mans@mansr.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox