From mboxrd@z Thu Jan 1 00:00:00 1970 From: sheriffesseson at gmail.com (Sheriff Esseson) Date: Thu, 25 Jul 2019 01:51:01 +0100 Subject: [Linux-kernel-mentees] [PATCH] Documentation: filesystem: fix "Removed Sysctls" table In-Reply-To: <20190723222142.GS7689@dread.disaster.area> References: <20190723114813.GA14870@localhost> <20190723074218.4532737f@lwn.net> <20190723145201.GA20658@localhost> <20190723222142.GS7689@dread.disaster.area> Message-ID: <20190725005101.GA21821@localhost> List-Id: On Wed, Jul 24, 2019 at 08:21:42AM +1000, Dave Chinner wrote: > On Tue, Jul 23, 2019 at 03:52:01PM +0100, Sheriff Esseson wrote: > > On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote: > > > On Tue, 23 Jul 2019 12:48:13 +0100 > > > Sheriff Esseson wrote: > > > > > > > the "Removed Sysctls" section is a table - bring it alive with ReST. > > > > > > > > Signed-off-by: Sheriff Esseson > > > > > > 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. > > The correct thing to do in that case is to reply to the original > patch and ask if it has been looked at. The usual way of doing this > is quoting the commit message and replying with a "Ping?" comment > to bump it back to the top of everyone's mail stacks. > > But, again, 3 days is not a long time, people tend to be extremely > busy and might take a few days to get to reviewing non-critical > changes, and people may not even review patches during the merge > window. I'd suggest waiting a week before pinging a patch you've > sent if there's been no response.... Okay, Thanks Dave. > > Cheers, > > Dave. > -- > Dave Chinner > david at fromorbit.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: sheriffesseson@gmail.com (Sheriff Esseson) Date: Thu, 25 Jul 2019 01:51:01 +0100 Subject: [Linux-kernel-mentees] [PATCH] Documentation: filesystem: fix "Removed Sysctls" table In-Reply-To: <20190723222142.GS7689@dread.disaster.area> References: <20190723114813.GA14870@localhost> <20190723074218.4532737f@lwn.net> <20190723145201.GA20658@localhost> <20190723222142.GS7689@dread.disaster.area> Message-ID: <20190725005101.GA21821@localhost> List-Id: Content-Type: text/plain; charset="UTF-8" Message-ID: <20190725005101.TLYTk3lUMH1rRC95rYYnucM-nyYjzOAZfpy6WG2U6hM@z> On Wed, Jul 24, 2019 at 08:21:42AM +1000, Dave Chinner wrote: > On Tue, Jul 23, 2019 at 03:52:01PM +0100, Sheriff Esseson wrote: > > On Tue, Jul 23, 2019 at 07:42:18AM -0600, Jonathan Corbet wrote: > > > On Tue, 23 Jul 2019 12:48:13 +0100 > > > Sheriff Esseson wrote: > > > > > > > the "Removed Sysctls" section is a table - bring it alive with ReST. > > > > > > > > Signed-off-by: Sheriff Esseson > > > > > > 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. > > The correct thing to do in that case is to reply to the original > patch and ask if it has been looked at. The usual way of doing this > is quoting the commit message and replying with a "Ping?" comment > to bump it back to the top of everyone's mail stacks. > > But, again, 3 days is not a long time, people tend to be extremely > busy and might take a few days to get to reviewing non-critical > changes, and people may not even review patches during the merge > window. I'd suggest waiting a week before pinging a patch you've > sent if there's been no response.... Okay, Thanks Dave. > > Cheers, > > Dave. > -- > Dave Chinner > david at fromorbit.com