From: Harvey Harrison <harvey.harrison@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: please hold off 2.6.28 stuff
Date: Sun, 20 Jul 2008 23:13:41 -0700 [thread overview]
Message-ID: <1216620821.13328.14.camel@brick> (raw)
In-Reply-To: <20080721135108.d4ca4be5.sfr@canb.auug.org.au>
On Mon, 2008-07-21 at 13:51 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Andrew mentioned this and I just thought I would reinforce the message:
>
> Please do not put 2.6.28 code into linux-next until at least after -rc1.
> This will help Andrew's sanity :-)
I would say let -rc2 be the flag for putting things for the next (2.6.28) release
into -next. That would give akpm time to get his load in as well.
Between -rc1 and -rc2, he could look at -next to see what patches were
picked up by maintainers and what he'll still have to send in himself.
But it's not me doing the work :-)
Keep up the good work Stephen/AKPM.
Harvey
next prev parent reply other threads:[~2008-07-21 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 3:51 linux-next: please hold off 2.6.28 stuff Stephen Rothwell
2008-07-21 6:13 ` Harvey Harrison [this message]
2008-07-21 6:21 ` Stephen Rothwell
2008-07-21 6:29 ` Andrew Morton
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=1216620821.13328.14.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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