public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Louis <glouis@dynamicro.on.ca>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Paul P Komkoff Jr <i@stingr.net>, linux-kernel@vger.kernel.org
Subject: Re: SSSCA: We're in trouble now
Date: Sat, 2 Mar 2002 20:29:43 -0500	[thread overview]
Message-ID: <20020303012943.GA3130@athame.dynamicro.on.ca> (raw)
In-Reply-To: <20020302183041.P6075@stingr.net> <Pine.LNX.4.44L.0203021857380.2181-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.44L.0203021857380.2181-100000@imladris.surriel.com>

On 20020302 (Sat) at 1858:10 -0300, Rik van Riel wrote:
> On Sat, 2 Mar 2002, Paul P Komkoff Jr wrote:

> > unfortunately 98% don't care about such things. they sit on their
> > g-spots and drink vodka (or something). they DON'T NEED computers. or
> > anything else except their drinks.
> 
> vodka ?   I think you mean "budweiser" ...

Don't underrate that stuff, in the hands of the "blessed."  They sit
around and drink between 2 and 5 341ml aliquots of 3% beer and imagine
themselves emperors of the universe -- then they behave accordingly......

-- 
| G r e g  L o u i s          | gpg public key:      |
|   http://www.bgl.nu/~glouis |   finger greg@bgl.nu |

Header information for this message:
Subject: Re: SSSCA: We're in trouble now
     To: Rik van Riel <riel@conectiva.com.br>
     CC: Paul P Komkoff Jr <i@stingr.net>
 linux-kernel@vger.kernel.org
   From: Greg Louis <glouis@dynamicro.on.ca>

  reply	other threads:[~2002-03-03  1:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-02  0:21 SSSCA: We're in trouble now Thomas Hood
2002-03-02  8:35 ` Florian Weimer
2002-03-02 17:34   ` M. Edward (Ed) Borasky
2002-03-04  8:30   ` Helge Hafting
2002-03-04  9:40     ` Martin Eriksson
2002-03-04 17:02       ` Paul G. Allen
2002-03-06  4:41     ` Petro
2002-03-06  9:27       ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58   ` Rik van Riel
2002-03-03  1:29     ` Greg Louis [this message]
2002-03-06  4:51   ` Petro
2002-03-02 17:47 ` Jurgen Botz
2002-03-06  5:00   ` Petro
2002-03-06 16:42     ` Alan Cox
2002-03-06 18:24       ` Paul G. Allen
2002-03-06 23:56       ` Petro
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
2002-03-04 19:27 Jesse Pollard
2002-03-01 19:46 Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 20:30   ` Xavier Bestel
2002-03-01 21:29     ` Shawn Starr
2002-03-01 22:19       ` Alan Cox
2002-03-02  3:08         ` Neale Banks
2002-03-02  3:03           ` eddantes
2002-03-02 18:32           ` Alan Cox
2002-03-01 22:47       ` Florian Weimer
2002-03-02  2:59         ` Paul G. Allen
2002-03-06  4:26           ` Petro
2002-03-06  4:41             ` Trever L. Adams
2002-03-06 16:26               ` Rik van Riel
2002-03-06 17:03                 ` Richard B. Johnson
2002-03-06 18:16                 ` Paul G. Allen
2002-03-06 18:35                 ` Trever L. Adams
2002-03-07 22:54                 ` Florian Weimer
2002-03-08  2:12                   ` Tom Rauschenbach

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=20020303012943.GA3130@athame.dynamicro.on.ca \
    --to=glouis@dynamicro.on.ca \
    --cc=i@stingr.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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