mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Timothy D. Witham" <wookie@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Paul Larson <plars@linuxtestproject.org>,
	John Bradford <john@grabjohn.com>,
	davej@codemonkey.org.uk, edesio@ieee.org,
	lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	edesio@task.com.br
Subject: Re: 2.5.60 cheerleading...
Date: 20 Feb 2003 14:29:49 -0800	[thread overview]
Message-ID: <1045780188.1429.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20030213213850.GA22037@gtf.org>

Sorry about getting back on the thread late was off doing boring
management stuff.

But this is what PLM/STP does but right now it doesn't bother
to send the results to any list.

http://www.osdl.org/projects/26lnxstblztn/results/

Tim


On Thu, 2003-02-13 at 13:38, Jeff Garzik wrote:
> On Thu, Feb 13, 2003 at 03:16:29PM -0600, Paul Larson wrote:
> > Ideally, there should be no waiting around for replies.  The message is
> > sent, he starts whatever build/boot test cycle, checks for replies when
> > he's done and ready to release.  If nothing looks urgent enough to hold
> > it up, then he pushes the release.  I still don't see how this adds any
> > kind of terrible delay.
> 
> Outside suggestions to "improve" Linus's workflow usually fall upon deaf
> ears...
> 
> IMO to accomplish your goals, set up a test box with BitKeeper,
> constantly pulling and testing the latest 2.5.x BK trees.  If they
> crash, send full info to lkml.
> 
> Enough crash messages, and people will know automatically whether or not
> the kernel is good... and Linus didn't have to be bothered at all.
> 
> 	Jeff
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Timothy D. Witham - Lab Director - wookie@osdlab.org
Open Source Development Lab Inc - A non-profit corporation
15275 SW Koll Parkway - Suite H - Beaverton OR, 97006
(503)-626-2455 x11 (office)    (503)-702-2871     (cell)
(503)-626-2436     (fax)


  parent reply	other threads:[~2003-02-20 22:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 15:52 Jeff Garzik
2003-02-12 16:00 ` Paul Larson
2003-02-12 16:09   ` Jeff Garzik
2003-02-12 18:07 ` Dave Jones
2003-02-12 18:44   ` John Bradford
2003-02-12 18:17 ` Scott Robert Ladd
2003-02-12 18:41   ` John Bradford
2003-02-12 18:55   ` Dave Jones
2003-02-12 18:43 ` Paul Larson
2003-02-12 19:33   ` Edesio Costa e Silva
2003-02-13 15:29     ` Paul Larson
2003-02-13 15:54       ` Jörn Engel
2003-02-13 16:03       ` Dave Jones
2003-02-13 16:55         ` Paul Larson
2003-02-13 17:11           ` John Bradford
2003-02-13 18:04             ` Paul Larson
2003-02-13 18:23               ` John Bradford
2003-02-13 21:16                 ` Paul Larson
2003-02-13 21:38                   ` Jeff Garzik
2003-02-13 21:54                     ` John Bradford
2003-02-13 21:57                       ` Paul Larson
2003-02-13 22:11                         ` John Bradford
2003-02-13 22:20                         ` Valdis.Kletnieks
2003-02-13 22:39                           ` Paul Larson
2003-02-13 22:43                           ` Randy.Dunlap
2003-02-13 22:53                             ` Paul Larson
2003-02-13 22:58                           ` John Bradford
2003-02-14  6:36                           ` Paul Larson
2003-02-20 22:29                     ` Timothy D. Witham [this message]
2003-02-20 22:42                       ` Jeff Garzik
2003-02-20 22:46                         ` Timothy D. Witham
2003-02-14  1:21               ` Martin J. Bligh
2003-02-14  1:32                 ` Linus Torvalds
2003-02-14  3:24                   ` Mike Dresser
2003-02-14  9:08                   ` John Bradford
2003-02-14  4:10             ` Werner Almesberger
2003-02-13 17:06         ` 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=1045780188.1429.30.camel@localhost.localdomain \
    --to=wookie@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=edesio@ieee.org \
    --cc=edesio@task.com.br \
    --cc=jgarzik@pobox.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@linuxtestproject.org \
    --cc=torvalds@transmeta.com \
    /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®