From: NeilBrown <neilb@suse.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text
Date: Fri, 21 Dec 2018 11:33:21 +1100 [thread overview]
Message-ID: <87pntvu3am.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181220085403.5538683d@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Thu, Dec 20 2018, Jonathan Corbet wrote:
> On Mon, 10 Dec 2018 09:58:37 +1100
> NeilBrown <neilb@suse.com> wrote:
>
>> However we now have a stub section "Pathname lookup" which serves only
>> to introduce another stub sectoin "Pathname lookup in Linux", which does
>> little more than introduce the rest of the section.
>> This seems inelegant, and is probably why I went for the "include"
>> approach.
>>
>> What would you think of something more like the following?
>
> Sorry for the delay ... $EXCUSES ...
'tis the season for $EXCUSES
>
> This makes sense; I went ahead and applied it with your SOB on it; let me
> know if that's not what you wanted.
Perfect, thanks.
NeilBrown
>
> Thanks,
>
> jon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-12-21 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 0:55 [PATCH] Documentation: update path-lookup.md for parallel lookups NeilBrown
2018-11-20 16:38 ` Jonathan Corbet
2018-12-04 23:02 ` [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text NeilBrown
2018-12-04 23:04 ` [PATCH 2/2] Documentation: path-lookup - update externel refs NeilBrown
2018-12-05 19:46 ` [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text Jonathan Corbet
2018-12-05 21:00 ` NeilBrown
2018-12-06 17:09 ` Jonathan Corbet
2018-12-09 22:58 ` NeilBrown
2018-12-20 15:54 ` Jonathan Corbet
2018-12-21 0:33 ` NeilBrown [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=87pntvu3am.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=corbet@lwn.net \
--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).