From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: Define our preferred form for multiline comments
Date: Tue, 5 Jun 2018 11:55:14 +0200 [thread overview]
Message-ID: <20180605115514.65af4c41.cohuck@redhat.com> (raw)
In-Reply-To: <CAFEAcA80XzxdxLfwMUYLpHprX8L=AZyNDw1DiJKshhGvbFJLRA@mail.gmail.com>
On Tue, 5 Jun 2018 10:19:15 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 5 June 2018 at 08:46, Cornelia Huck <cohuck@redhat.com> wrote:
> > On Tue, 5 Jun 2018 06:33:22 +0200
> > Thomas Huth <thuth@redhat.com> wrote:
> >> Anyway, could we either use that dense format or the kernel-style
> >> multi-lines-comment format, please? Mixing it asymmetrically is just ugly.
> >
> > I'd vote for the kernel style, then.
>
> I don't particularly object to the kernel style (though it's not
> how I personally default to writing comments). I just didn't want
> to rule a huge chunk of our existing comments as out-of-standard
> for what I see as a relatively minor divergence in form --
> we do have a lot of no-leading-separate-/* comments. I can live
> with mandating kernel-style if it means we can rule out GNU-form
> and other weirdnesses though :-)
Yes, we should be flexible... as long as it isn't GNU :)
Whatever we end up with, we should take care that we don't get zillions
of "cleanup" patches that don't add value... something like "no need to
change preexisting comments, unless you're touching the code anyway".
next prev parent reply other threads:[~2018-06-05 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 16:21 [Qemu-devel] [PATCH] CODING_STYLE: Define our preferred form for multiline comments Peter Maydell
2018-06-04 18:01 ` John Snow
2018-06-04 19:10 ` Philippe Mathieu-Daudé
2018-06-05 1:17 ` Alex Williamson
2018-06-05 4:33 ` Thomas Huth
2018-06-05 7:46 ` Cornelia Huck
2018-06-05 9:19 ` Peter Maydell
2018-06-05 9:49 ` Thomas Huth
2018-06-05 9:55 ` Cornelia Huck [this message]
2018-06-07 12:02 ` Markus Armbruster
2018-06-11 11:22 ` Kevin Wolf
2018-06-07 12:40 ` Stefan Hajnoczi
2018-06-07 13:25 ` Peter Maydell
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=20180605115514.65af4c41.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).