From: Rob Landley <rob@landley.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Willy Tarreau <w@1wt.eu>, Ben Hutchings <ben@decadent.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] Documentation: update references to v2.6.x in development-process
Date: Tue, 23 Jul 2013 18:20:07 -0500 [thread overview]
Message-ID: <1374621607.3031.3@driftwood> (raw)
In-Reply-To: <51E69D50.10000@windriver.com> (from paul.gortmaker@windriver.com on Wed Jul 17 08:34:08 2013)
On 07/17/2013 08:34:08 AM, Paul Gortmaker wrote:
> On 13-07-16 01:33 PM, Jonathan Corbet wrote:
> > On Mon, 15 Jul 2013 19:34:44 -0400
> > Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> >> The last mainline release of a v2.6.x kernel was back in May 2011.
> >> Here we update references to be 3.x based, which also means
> updating
> >> some dates and statistics.
> >
> > Ccing the author of the document never hurts :)
>
> It might be worth sticking an entry in MAINTAINERS for that dir.
> If one had asked me who wrote it, I probably would have recalled that
> info, but instead I just out of habit ran get_maintainers...
I note that every file people stick a MAINTAINERS entry for in
Documentation is one that I _don't_ bother with. Just FYI.
(Yes, 5 days behind on the list, but catching up...)
Rob
prev parent reply other threads:[~2013-07-23 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 23:34 [PATCH] Documentation: update references to v2.6.x in development-process Paul Gortmaker
2013-07-16 0:15 ` Stephen Rothwell
2013-07-16 2:13 ` Paul Gortmaker
2013-07-16 3:50 ` Stephen Rothwell
2013-07-16 4:44 ` Paul Gortmaker
2013-07-16 4:14 ` Ben Hutchings
2013-07-16 17:33 ` Jonathan Corbet
2013-07-17 13:34 ` Paul Gortmaker
2013-07-23 23:20 ` Rob Landley [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=1374621607.3031.3@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sfr@canb.auug.org.au \
--cc=w@1wt.eu \
/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