mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, kaber@trash.net,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [bug] build failures, git trees
Date: Mon, 21 Apr 2008 09:26:48 -0700	[thread overview]
Message-ID: <20080421092648.943a871b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080421.015837.35795810.davem@davemloft.net>

On Mon, 21 Apr 2008 01:58:37 -0700 (PDT) David Miller wrote:

<deletia>

> If you really cared, you would run your randconfig system on, for
> example, the linux-next and -mm trees, which I've specifically
> suggested and you've specifically ignored.  And there is no
> coincidence to that.

I do randconfigs on -mm and linux-next.  I report most* of the
build problems ... and as far as I can tell, they are mostly
ignored (especially in linux-next).

*: I don't report Voyager/Visual WS/NUMA-Q build errors.
Maybe they will just disappear one day.
I also don't report drivers/media/ build errors. They are too easy
to reproduce.  :(

IMO having -mm and linux-next is a diluting factor+.  They dilute
both build and boot testing of the other one and of mainline
-rcs.  Yes, they have their purposes, but it would be Very Good
if we could get to the point of having -mm built on top of
linux-next (e.g.) instead of it just being a separate tree.

+: Yes, there are other diluting factors, like having over 100 git
trees that someone may potentially request testing of.

---
~Randy

  parent reply	other threads:[~2008-04-21 16:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 10:00 [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Ingo Molnar
2008-04-19 10:03 ` David Miller
2008-04-19 10:39   ` Ingo Molnar
2008-04-19 11:09     ` David Miller
2008-04-21  8:22       ` Ingo Molnar
2008-04-21  8:58         ` David Miller
2008-04-21 11:14           ` Ingo Molnar
2008-04-21 16:26           ` Randy Dunlap [this message]
2008-04-21 21:42             ` [bug] build failures, git trees David Miller
2008-04-21 11:18         ` [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Patrick McHardy
2008-04-21 19:31           ` Ingo Molnar
2008-04-21  8:14     ` Jeff Garzik
2008-04-21 13:39       ` Ingo Molnar
2008-04-22  2:20         ` Herbert Xu
2008-04-19 10:07 ` David Miller
2008-04-19 10:41   ` Ingo Molnar
2008-04-19 11:10     ` David Miller
2008-04-19 10:44   ` Jan Engelhardt
2008-04-19 11:11     ` David Miller
2008-04-19 16:38   ` Patrick McHardy
2008-04-20  0:54     ` David Miller
2008-04-21  7:23 ` Jeff Garzik

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=20080421092648.943a871b.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /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®