mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: plars@linuxtestproject.org, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com, edesio@task.com.br
Subject: Re: 2.5.60 cheerleading...
Date: Thu, 13 Feb 2003 14:43:18 -0800	[thread overview]
Message-ID: <20030213144318.3ddcf2a6.rddunlap@osdl.org> (raw)
In-Reply-To: <200302132220.h1DMKtFT011682@turing-police.cc.vt.edu>

On Thu, 13 Feb 2003 17:20:55 -0500
Valdis.Kletnieks@vt.edu wrote:

| On Thu, 13 Feb 2003 15:57:56 CST, Paul Larson said:
| 
| > Since Linus hasn't chimed in yet, I'm guessing that's exactly what
| > happened.  I'm not trying to improve his workflow, but rather the
| > workflow of anyone who might be interested in getting more involved in
| > 2.5 testing.
| 
| What would help a lot of people (certainly me, at least), would be if
| somebody kept a well-publicized "already known errata" list along with
| (possibly unofficial) work-around patches.  Something along the line of:
| 
| compile fails in drivers/widget/fooby.c with error:
| undefined structure member 'blat' in line 1149.
| To fix:   apply <this patch>

Yes, I agree, that would be helpful.

I try to keep current lkml/etc patches for fixes/cleanups to the
latest kernel, and I've thought about a way to post them, but it's
too time-consuming a task, especially when it's not one's job
to do that.


| On Thu, 13 Feb 2003 22:11:17 +0000 (GMT), John Bradford said:
| 
| > You can always use 2.5.X-BK1 to get the fixes that we would probably
| > have been in 2.5.X if Linus had done more extensive testing on it
| > before releasing it.
| 
| Almost but not quite what I meant - unless -BK1 is reserved for after-release
| whoops and doesn't contain "new stuff for release N+1".   If -BK1 is only
| bugfixes, that would be good.  


--
~Randy

  parent reply	other threads:[~2003-02-13 22:37 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 [this message]
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=20030213144318.3ddcf2a6.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=edesio@task.com.br \
    --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®