All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tony Luck" <tony.luck@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
	alan@lxorguk.ukuu.org.uk, greg@kroah.com, 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 16:53:51 -0700	[thread overview]
Message-ID: <12c511ca0810151653p535d5ae4j297cf5b41900a4ba@mail.gmail.com> (raw)
In-Reply-To: <20081015164139.ebcd24c6.akpm@linux-foundation.org>

> Yes, but then people would end up being based on linux-next, and that's
> a pretty rubbery target with all the rebasing and trees getting
> dropped, etc.  And they'd accidentally end up having to actually
> compile and run linux-next, shock-horror-oh-the-humanity.

I built and booted linux-next a couple of times a week or so
for ia64.  Most of the time it worked just fine.  I found a few
build problems, but only three run-time problems. My boot
log shows 49 successful boots of linux-next based kernels
from 2.6.25-rc2 to 2.6.27-rc6

But perhaps less people are working on breaking ia64 :-)

-Tony

  reply	other threads:[~2008-10-15 23:53 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
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 [this message]
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=12c511ca0810151653p535d5ae4j297cf5b41900a4ba@mail.gmail.com \
    --to=tony.luck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --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.