From: Greg KH <greg@kroah.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: is the weeks before -rc1 the time to really be working on -next?
Date: Wed, 15 Oct 2008 13:30:38 -0700 [thread overview]
Message-ID: <20081015203038.GA14959@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810152202230.25933@anakin>
On Wed, Oct 15, 2008 at 10:04:17PM +0200, Geert Uytterhoeven wrote:
> On Wed, 15 Oct 2008, Greg KH wrote:
> > Just wondering, I know that -next is failing right now, and is a major
> > pain to produce, but that seems to be primarily due to all of the
> > subsystems merging with Linus right now.
> >
> > So does it even make sense to try to create a -next during the 2 weeks
> > of the major merge window? It seems to just cause you a whole lot of
> > work, that in the end, is mostly unecessary as all of the subsystem
> > maintainers are doing the merging themselves as trees move into Linus's
> > tree?
>
> I don't know if it's worth the effort...
>
> However, we definitely missed linux-next during the last few weeks, seeing
> things getting into mainline that don't even survive simple compile tests.
Oh I agree, I missed it a lot the past few weeks, it's amazing how much
we already started to rely on it in such a short time. That shows how
valuable the effort is.
Keep it up, I just don't want to see Stephen burn out during the pre-rc1
time period when it might not make as much sense to be trying to create
the tree.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-15 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:40 is the weeks before -rc1 the time to really be working on -next? Greg KH
2008-10-15 20:04 ` Geert Uytterhoeven
2008-10-15 20:30 ` Greg KH [this message]
2008-10-15 21:56 ` Andrew Morton
2008-10-15 22:08 ` Rafael J. Wysocki
2008-10-15 22:36 ` Alan Cox
2008-10-15 22:53 ` Andrew Morton
2008-10-15 23:08 ` David Miller
2008-10-15 23:41 ` Andrew Morton
2008-10-15 23:53 ` Tony Luck
2008-10-15 23:56 ` David Miller
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=20081015203038.GA14959@kroah.com \
--to=greg@kroah.com \
--cc=geert@linux-m68k.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 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.