From: Jonathan Corbet <corbet@lwn.net>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH] stable: Update documentation to clarify preferred procedure
Date: Fri, 22 May 2015 09:40:39 -0600 [thread overview]
Message-ID: <20150522094039.2a5d0914@lwn.net> (raw)
In-Reply-To: <1431547267-24375-1-git-send-email-christoffer.dall@linaro.org>
On Wed, 13 May 2015 22:01:07 +0200
Christoffer Dall <christoffer.dall@linaro.org> wrote:
> Clearly specify that option 1 is strongly preferred so that developers
> understand that option 2 or 3 should only be used when absolutely
> required.
Applied to the docs tree. I tweaked the changelog a bit, though, since
"option 1" means little outside of the context of the file itself.
Thanks,
jon
next prev parent reply other threads:[~2015-05-22 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:01 [PATCH] stable: Update documentation to clarify preferred procedure Christoffer Dall
2015-05-22 15:40 ` Jonathan Corbet [this message]
2015-05-24 9:52 ` Christoffer Dall
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=20150522094039.2a5d0914@lwn.net \
--to=corbet@lwn.net \
--cc=christoffer.dall@linaro.org \
--cc=gregkh@linuxfoundation.org \
--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).