mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: linux-kernel@vger.kernel.org, Coywolf Qi Hunt <coywolf@gmail.com>
Subject: Re: keep in sync with -mm tree?
Date: Tue, 8 Nov 2005 00:39:27 -0800	[thread overview]
Message-ID: <20051108003927.73465450.akpm@osdl.org> (raw)
In-Reply-To: <43706127.8020304@reub.net>

Reuben Farrelly <reuben-lkml@reub.net> wrote:
>

Please retain the cc line.

> On 8/11/2005 4:00 p.m., Andrew Morton wrote:
> > Coywolf Qi Hunt <coywolf@gmail.com> wrote:
> >> Hello,
> >>
> >> We can always keep in sync with the current Linus tree through his git
> >> tree. But from where can we keep in sync with the current -mm tree?
> >> ie, when somethings added to -mm, how do we get that too?
> > 
> > You can't.  The patches in -mm spend 90% of their time in an untested,
> > often-doesn't-compile state.  It's only in the 24-48 hours preceding a
> > release that I actually start build- and run-time testing it all.
> 
> Would it be at all useful if a small (and for feedback purposes only possibly 
> known) subset of users were to give the -mm releases a basic compile and build 
> before a proper -mm is released?  ie in the 24 hours preceding a formal -mm 
> release, to shake out the most obvious brown paper bag problems?  I know -mm 
> is a testbed but still, it must surely be better if the big bulk of those 
> (unknown number x) people who try it don't need to further patch it to get it 
> to at least build.  It also allows comments like "EDAC is known to not compile 
> on i386 with SMP, we are bugging Alan already about it" to be clearly stated 
> at the time it is released.
> 
> Personally I seem to have my share of compile, symbol and oopses that are 
> fairly obvious and are visible within 5 mins of booting up, and I'd be willing 
> to spare 15 mins once every couple of weeks or so to do a primitive regression 
> test on this and report back.  I can build on i386 and possibly x86_64 if need be.
> 
> Andrew, what do you think?

Maybe.  I'll take a look at uploading a nightly rollup as well.

> >> The only way now seems to check the mm-commits list. Is it possible to
> >> expose akpm's working folder somewhere for convenience?
> > 
> > Well I suppose I could upload stuff to
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ daily.  Then it's
> > trivial to install mm-of-the-day as a quilt series.
> > 
> > <does crontab -e>
> > 
> > Let me know how it goes..
> 
> Last time I tried a broken-out- tarball I ended up watching a heap of fuzzy 
> apply's then a part of the patch which was entirely rejected, leaving only the 
> first half of the broken-out mm patch applied and my tree in a busted half 
> patched state.

That would be atypicel ;)

  reply	other threads:[~2005-11-08  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56rz6-8re-25@gated-at.bofh.it>
     [not found] ` <56rSs-mJ-3@gated-at.bofh.it>
2005-11-08  8:26   ` Reuben Farrelly
2005-11-08  8:39     ` Andrew Morton [this message]
2005-11-09  0:27     ` Paul Jackson
2005-11-08  2:35 Coywolf Qi Hunt
2005-11-08  2:50 ` Andrew Morton
2005-11-08  3:15   ` Paul Jackson
2005-12-02  3:22     ` Coywolf Qi Hunt

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=20051108003927.73465450.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-lkml@reub.net \
    /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

all inboxes | Powered by JetHome®