From: Sheriff Esseson <sheriffesseson@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
"supporter:XFS FILESYSTEM" <linux-xfs@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Documentation: filesystem: fix "Removed Sysctls" table
Date: Tue, 23 Jul 2019 15:52:01 +0100 [thread overview]
Message-ID: <20190723145201.GA20658@localhost> (raw)
In-Reply-To: <20190723074218.4532737f@lwn.net>
On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote:
> On Tue, 23 Jul 2019 12:48:13 +0100
> Sheriff Esseson <sheriffesseson@gmail.com> wrote:
>
> > the "Removed Sysctls" section is a table - bring it alive with ReST.
> >
> > Signed-off-by: Sheriff Esseson <sheriffesseson@gmail.com>
>
> So this appears to be identical to the patch you sent three days ago; is
> there a reason why you are sending it again now?
>
> Thanks,
>
> jon
Sorry, I was think the patch went unnoticed during the merge window - I could
not find a response.
WARNING: multiple messages have this Message-ID (diff)
From: sheriffesseson at gmail.com (Sheriff Esseson)
Subject: [Linux-kernel-mentees] [PATCH] Documentation: filesystem: fix "Removed Sysctls" table
Date: Tue, 23 Jul 2019 15:52:01 +0100 [thread overview]
Message-ID: <20190723145201.GA20658@localhost> (raw)
In-Reply-To: <20190723074218.4532737f@lwn.net>
On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote:
> On Tue, 23 Jul 2019 12:48:13 +0100
> Sheriff Esseson <sheriffesseson at gmail.com> wrote:
>
> > the "Removed Sysctls" section is a table - bring it alive with ReST.
> >
> > Signed-off-by: Sheriff Esseson <sheriffesseson at gmail.com>
>
> So this appears to be identical to the patch you sent three days ago; is
> there a reason why you are sending it again now?
>
> Thanks,
>
> jon
Sorry, I was think the patch went unnoticed during the merge window - I could
not find a response.
WARNING: multiple messages have this Message-ID (diff)
From: sheriffesseson@gmail.com (Sheriff Esseson)
Subject: [Linux-kernel-mentees] [PATCH] Documentation: filesystem: fix "Removed Sysctls" table
Date: Tue, 23 Jul 2019 15:52:01 +0100 [thread overview]
Message-ID: <20190723145201.GA20658@localhost> (raw)
Message-ID: <20190723145201.pauE8QOusf1JA-hylJzUdiyyZmL2D_IeM2moPBZd_3k@z> (raw)
In-Reply-To: <20190723074218.4532737f@lwn.net>
On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote:
> On Tue, 23 Jul 2019 12:48:13 +0100
> Sheriff Esseson <sheriffesseson at gmail.com> wrote:
>
> > the "Removed Sysctls" section is a table - bring it alive with ReST.
> >
> > Signed-off-by: Sheriff Esseson <sheriffesseson at gmail.com>
>
> So this appears to be identical to the patch you sent three days ago; is
> there a reason why you are sending it again now?
>
> Thanks,
>
> jon
Sorry, I was think the patch went unnoticed during the merge window - I could
not find a response.
WARNING: multiple messages have this Message-ID (diff)
From: Sheriff Esseson <sheriffesseson@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
"supporter:XFS FILESYSTEM" <linux-xfs@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Documentation: filesystem: fix "Removed Sysctls" table
Date: Tue, 23 Jul 2019 15:52:01 +0100 [thread overview]
Message-ID: <20190723145201.GA20658@localhost> (raw)
In-Reply-To: <20190723074218.4532737f@lwn.net>
On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote:
> On Tue, 23 Jul 2019 12:48:13 +0100
> Sheriff Esseson <sheriffesseson@gmail.com> wrote:
>
> > the "Removed Sysctls" section is a table - bring it alive with ReST.
> >
> > Signed-off-by: Sheriff Esseson <sheriffesseson@gmail.com>
>
> So this appears to be identical to the patch you sent three days ago; is
> there a reason why you are sending it again now?
>
> Thanks,
>
> jon
Sorry, I was think the patch went unnoticed during the merge window - I could
not find a response.
next prev parent reply other threads:[~2019-07-23 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 11:48 [PATCH] Documentation: filesystem: fix "Removed Sysctls" table Sheriff Esseson
2019-07-23 11:48 ` [Linux-kernel-mentees] " Sheriff Esseson
2019-07-23 11:48 ` sheriffesseson
2019-07-23 13:42 ` Jonathan Corbet
2019-07-23 13:42 ` [Linux-kernel-mentees] " Jonathan Corbet
2019-07-23 13:42 ` corbet
2019-07-23 14:52 ` Sheriff Esseson [this message]
2019-07-23 14:52 ` Sheriff Esseson
2019-07-23 14:52 ` [Linux-kernel-mentees] " Sheriff Esseson
2019-07-23 14:52 ` sheriffesseson
2019-07-23 22:21 ` Dave Chinner
2019-07-23 22:21 ` [Linux-kernel-mentees] " Dave Chinner
2019-07-23 22:21 ` david
2019-07-25 0:51 ` sheriffesseson
2019-07-25 0:51 ` Sheriff Esseson
2019-07-26 20:51 ` Jonathan Corbet
2019-07-26 20:51 ` [Linux-kernel-mentees] " Jonathan Corbet
2019-07-26 20:51 ` corbet
-- strict thread matches above, loose matches on Subject: below --
2019-07-20 17:29 Sheriff Esseson
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=20190723145201.GA20658@localhost \
--to=sheriffesseson@gmail.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.