All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: 3 Dec 2002 14:13:33 GMT	[thread overview]
Message-ID: <asie6d$5dr$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20021203121521.GB30431@suse.de

In article <20021203121521.GB30431@suse.de>,
Dave Jones  <davej@codemonkey.org.uk> wrote:

| "xxx doesn't work in 2.5.47", then Rusty's module rewrite happened,
| and the tester didn't (or couldn't) see if it got fixed in subsequent
| kernels. I'll send out pings to such reports when they get to something
| like 5 kernels old. If the problem then doesn't get re-ACKed, I'll
| close it. Any objections?

  Since you are doing the work, you should set your own policy. I might
suggest that if we revert the module stuff to something working in
fewer than five versions you might ping then, and you might wait to
drop stuff of the "xxx fails in 2.5.47 as a module" until modules work
again or we officially go to a monolythic kernel.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2002-12-03 14:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03  7:24 lkml, bugme.osdl.org? Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones
2002-12-03 14:13   ` bill davidsen [this message]
2002-12-03 18:09   ` Tupshin Harper
2002-12-04 11:58   ` Dr. David Alan Gilbert
2002-12-04 12:35     ` Russell King
2002-12-04 12:42     ` Dave Jones
2002-12-04 18:32       ` Dr. David Alan Gilbert
2002-12-04 22:20         ` Russell King
2002-12-05  9:15           ` David Woodhouse
2002-12-05  9:25             ` William Lee Irwin III
2002-12-05  9:34               ` David Woodhouse
2002-12-05  9:35                 ` William Lee Irwin III
2002-12-05 14:24       ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh

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='asie6d$5dr$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.