From: "Jack Johnson" <knapjack@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: do YOU know how to deal with an aggressive rabbit?
Date: Fri, 13 Oct 2006 10:38:57 -0700 [thread overview]
Message-ID: <6e35c0620610131038w4c3a0b33nf2ccd8aa37e4497@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180610131013i522df724r4844ff294a06dbf8@mail.gmail.com>
On 10/13/06, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> well, do you?
Isn't that called Hasenpfeffer?
Or is it Lapin à la Moutarde?
-Jack
next prev parent reply other threads:[~2006-10-13 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 17:13 andrey mirtchovski
2006-10-13 17:38 ` Jack Johnson [this message]
2006-10-13 17:49 ` Paul Lalonde
2006-10-14 1:53 ` Ignacio Torres Masdeu
2006-10-14 4:36 ` Bruce Ellis
2006-10-13 18:58 ` Joel Salomon
2006-10-13 20:03 ` Jack Johnson
2006-10-13 20:15 ` Gabriel Diaz
2006-10-13 23:45 ` Bruce Ellis
2006-10-14 0:16 ` Lucas James
2006-10-15 0:30 ` Jack Johnson
2006-10-15 7:09 ` andrey mirtchovski
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=6e35c0620610131038w4c3a0b33nf2ccd8aa37e4497@mail.gmail.com \
--to=knapjack@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).