From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] docs: Update the location of the LF NDA program
Date: Fri, 5 Jun 2020 12:40:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2006051238540.11918@felia> (raw)
In-Reply-To: <20200603161407.0ec41084@lwn.net>
On Wed, 3 Jun 2020, Jonathan Corbet wrote:
> The link to the Linux Foundation NDA program got broken in one of their
> web-site thrashups; now that the information is back online, point to its
> current location. This should last until the next thrashup...
>
> Cc: stable@vger.kernel.org
> Reported-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
For what it is worth on a one-line change,
Reviewed-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
I checked that the new URL now resolves to the document on the NDA
program.
Lukas
> ---
> Documentation/process/3.Early-stage.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/3.Early-stage.rst b/Documentation/process/3.Early-stage.rst
> index be00716071d4..7067abbd75bc 100644
> --- a/Documentation/process/3.Early-stage.rst
> +++ b/Documentation/process/3.Early-stage.rst
> @@ -216,7 +216,7 @@ a non-disclosure agreement. The Linux Foundation operates an NDA program
> designed to help with this sort of situation; more information can be found
> at:
>
> - http://www.linuxfoundation.org/en/NDA_program
> + https://www.linuxfoundation.org/nda/
>
> This kind of review is often enough to avoid serious problems later on
> without requiring public disclosure of the project.
> --
> 2.26.2
>
>
prev parent reply other threads:[~2020-06-05 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 22:14 [PATCH] docs: Update the location of the LF NDA program Jonathan Corbet
2020-06-05 10:40 ` Lukas Bulwahn [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=alpine.DEB.2.21.2006051238540.11918@felia \
--to=lukas.bulwahn@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@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