public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Hans Holmberg <hans@pixelmunchies.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/Kconfig.debug: correct documentation paths
Date: Tue, 13 Dec 2016 16:41:51 -0700	[thread overview]
Message-ID: <20161213164151.2aea89a4@lwn.net> (raw)
In-Reply-To: <20161213144054.GA5579@Gaia>

On Tue, 13 Dec 2016 15:40:57 +0100
Hans Holmberg <hans@pixelmunchies.com> wrote:

> A bunch of documentation files have moved, correct the paths.

Good catch.  Guess I'm as good a messenger as anybody else for this one;
applied to docs-next, thanks.

jon

  reply	other threads:[~2016-12-13 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 14:40 [PATCH] lib/Kconfig.debug: correct documentation paths Hans Holmberg
2016-12-13 23:41 ` Jonathan Corbet [this message]
2017-02-24  8:36 ` Krzysztof Kozlowski
2017-02-24 17:21   ` Jonathan Corbet
2017-02-24 17:29     ` Krzysztof Kozlowski
2017-03-16  8:29     ` Hans Holmberg

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=20161213164151.2aea89a4@lwn.net \
    --to=corbet@lwn.net \
    --cc=hans@pixelmunchies.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