All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Bradford <john@grabjohn.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@osdl.org
Subject: Re: Linux v2.6.0-test1
Date: 14 Jul 2003 13:40:36 +0100	[thread overview]
Message-ID: <1058186436.561.54.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200307141150.h6EBoe1P000738@81-2-122-30.bradfords.org.uk>

On Llu, 2003-07-14 at 12:50, John Bradford wrote:
> > Then you'll just have to wait a few months
> 
> Oh well, it just seems strange to be asking people to test
> 2.6.0-root-my-box, without making the consequences a bit clearer.

Its 2.6.0 locally root my box, not remotely root my box, although remote
crash bugs exist in at least one situation


  parent reply	other threads:[~2003-07-14 12:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 11:50 Linux v2.6.0-test1 John Bradford
2003-07-14 11:53 ` Dave Jones
2003-07-14 12:00   ` William Lee Irwin III
2003-07-14 12:39     ` Alan Cox
2003-07-14 12:47       ` William Lee Irwin III
2003-07-14 12:47         ` Alan Cox
2003-07-14 13:48         ` Linux v2.6.0-test1 [[Fwd: [Full-Disclosure] Linux 2.4.x execve() file read race vulnerability]] David R. Piegdon
2003-07-14 12:40 ` Alan Cox [this message]
2003-07-14 16:55 ` Linux v2.6.0-test1 Kurt Wall
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15  7:52 Dirk Meul
2003-07-16  6:32 ` Martin Schlemmer
2003-07-14 11:39 John Bradford
2003-07-14 11:33 ` Alan Cox
2003-07-14 13:56   ` Marcelo Tosatti
2003-07-14 15:07     ` Alan Cox
2003-07-14 16:44       ` Marcelo Tosatti
2003-07-14 11:01 John Bradford
2003-07-14 11:15 ` Alan Cox
2003-07-14  3:59 Linus Torvalds
2003-07-15  4:11 ` Matt Reppert
2003-07-15 10:56   ` Dave Jones
2003-07-15 17:38     ` Dominik Brodowski
2003-07-15 18:11       ` Dave Jones
2003-05-22 20:12 DMA gone on ALI 1533 Peter
2003-07-14  7:26 ` Linux v2.6.0-test1 Peter

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=1058186436.561.54.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.