From: Jonathan Corbet <corbet@lwn.net>
To: Gary R Hook <gary.hook@amd.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation/CodingStyle: Add an example for braces
Date: Mon, 26 Mar 2018 10:32:49 -0600 [thread overview]
Message-ID: <20180326103249.42789cdb@lwn.net> (raw)
In-Reply-To: <724fc548-0e40-11a3-2a9b-3dd0db0de880@amd.com>
On Mon, 26 Mar 2018 11:28:03 -0500
Gary R Hook <gary.hook@amd.com> wrote:
> Submitting a v3 because the example could better illuminate the options
> by using loop construct inside of an if, addressing Jani's point but
> without opening the door to later criticism.
>
> I also like the verbage in v2/3 better, but I'll let Jonathan make the call.
As I told you, I was applying the first version; I did that last week.
> BTW which tree should these be developed against? I used torvalds, but
> I'm not entirely sure that was the proper one?
The MAINTAINERS file will (almost) always answer that question for
you:
T: git git://git.lwn.net/linux.git docs-next
For a patch like this it doesn't matter, since there's is no other work on
the file to conflict with.
THanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-26 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 20:04 [PATCH v2] Documentation/CodingStyle: Add an example for braces Gary R Hook
2018-03-21 15:17 ` Jonathan Corbet
2018-03-22 9:12 ` Jani Nikula
2018-03-26 16:28 ` Gary R Hook
2018-03-26 16:32 ` Jonathan Corbet [this message]
2018-03-26 16:49 ` Gary R Hook
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=20180326103249.42789cdb@lwn.net \
--to=corbet@lwn.net \
--cc=gary.hook@amd.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).