From: Paul Larson <plars@linuxtestproject.org>
To: John Bradford <john@grabjohn.com>
Cc: 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: 13 Feb 2003 15:16:29 -0600 [thread overview]
Message-ID: <1045170999.28493.57.camel@plars> (raw)
In-Reply-To: <200302131823.h1DINeZh016257@darkstar.example.net>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Thu, 2003-02-13 at 12:23, John Bradford wrote:
> > > > How about a quick note out to lkml that says "The current bk is
> > > > what I'm going to release at <NN Time> today unless someone
> > > > gives me a good reason not to."?
> > > Why? That would just delay releases, and make more work for Linus.
> > What I just suggested would be a short 1 line note to lkml. I know he's
> > very busy, but what's that, like 10 seconds?
>
> 10 seconds, plus the time waiting around for replies, and the time
> spent reading the replies.
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.
-Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-02-13 21:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 2.5.60 cheerleading 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 [this message]
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
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=1045170999.28493.57.camel@plars \
--to=plars@linuxtestproject.org \
--cc=davej@codemonkey.org.uk \
--cc=edesio@ieee.org \
--cc=edesio@task.com.br \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.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