mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] intermediate SCSI updates
Date: Tue, 14 Oct 2008 10:44:59 +1100	[thread overview]
Message-ID: <20081014104459.715fe7a2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0810131416410.3288@nehalem.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

Hi Linus,

On Mon, 13 Oct 2008 14:22:13 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Is linux-next coverage REALLY so weak that it doesn't even test the 
> default config options, much less any random options? What's the point of 
> linux-next then?

Check the results page of the automated builds I do
(http://kisskb.ellerman.id.au/linux-next) - I don't think that the
compile coverage is weak ...  Of course, if people don't read the
results ...

Those automated builds are done after the release.  Before the release,
the tree is built for ppc64_defconfig, powerpc allnoconfig, 44x_defconfig
for powerpc, allmodconfig for x86_64 and defconfig for i386, sparc and
sparc64.

All this is mentioned in my release notes every day.

> Again, the date on that thing is claimed to be September 19th, although it 
> was obviously committed later.

September 19 (Australian time) was the last linux-next release.  I don't
know off the top of my head if the particular patch in question was in
next-20080919, but it did contain a version of James' post merge patches.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-10-13 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 14:45 James Bottomley
2008-10-13 17:22 ` Linus Torvalds
2008-10-13 19:20   ` James Bottomley
2008-10-13 21:22     ` Linus Torvalds
2008-10-13 22:02       ` Paul Mackerras
2008-10-13 22:22       ` Martin K. Petersen
2008-10-13 23:44       ` Stephen Rothwell [this message]
2008-10-14 12:49       ` James Bottomley
2008-10-17 15:11 ` [GIT PATCH] intermediate SCSI updates (v2) James Bottomley

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=20081014104459.715fe7a2.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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®