All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Landley <rob@landley.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>
Subject: Re: [PATCH] Documentation: update references to v2.6.x in development-process
Date: Tue, 16 Jul 2013 00:44:07 -0400	[thread overview]
Message-ID: <20130716044406.GD26761@windriver.com> (raw)
In-Reply-To: <20130716135015.62f64a255f3de76946651222@canb.auug.org.au>

[Re: [PATCH] Documentation: update references to v2.6.x in development-process] On 16/07/2013 (Tue 13:50) Stephen Rothwell wrote:

> Hi Paul,
> 
> On Mon, 15 Jul 2013 22:13:50 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> > On a similar note, I was thinking about the recent thread on linux-next
> > where we were indicating that people shouldn't rebase linux-next content
> > on a whim, and that new devel (vs. bugfix) content shouldn't appear in
> > the linux-next content during the merge window.  There is no question
> > that the linux-next process is integral to the main flow of patches to
> > mainline, so I think Documentation/development-process/2.Process (the
> > same file) should also capture those points in the linux-next section.
> > Do you have some pre-canned text we can insert there, or should I draft
> > something up for you to review?
> 
> The latter would be certainly easier for me :-)  If that is not easy, let
> me know and I will write something (even without swearing ;-)).

I'll do something for the latter, but I can't promise to refrain from
swearing...  ;-)

Thanks,
Paul.
--

> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au



  reply	other threads:[~2013-07-16  4:44 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 [this message]
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

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=20130716044406.GD26761@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --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 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.