From: Felix Lee <flee@teleport.com>
Cc: ding@gnus.org
Subject: Re: K
Date: Sat, 02 May 1998 19:57:18 -0600 [thread overview]
Message-ID: <199805030312.UAA03482@mail1.teleport.com> (raw)
In-Reply-To: <0f7m4586bw.fsf@fenris.mjolner.dk> on 02 May 1998 09:44:51 +0200.
Lars Balker Rasmussen <lbr@mjolner.dk>:
> I'll bind C-c C-b to a function that sends a bugreport with each of
> "AAA", "BBB", ..., "ZZZ" prepended to my name. Let's see you worm out
> of that one! Ha!
bet that triggers the spam detector and you'll get ignored
completely.
--
next prev parent reply other threads:[~1998-05-03 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-26 22:29 K Lars Magne Ingebrigtsen
1998-04-27 14:29 ` K Wes Hardaker
1998-04-28 0:25 ` K Lars Magne Ingebrigtsen
1998-04-28 18:33 ` K Paul Franklin
1998-05-01 16:40 ` K Lars Magne Ingebrigtsen
1998-05-01 19:03 ` K Lars Balker Rasmussen
1998-05-01 19:37 ` K Lars Magne Ingebrigtsen
1998-05-01 21:58 ` K Wes Hardaker
1998-05-01 22:56 ` K Lars Magne Ingebrigtsen
1998-05-02 7:44 ` K Lars Balker Rasmussen
1998-05-03 1:57 ` Felix Lee [this message]
1998-05-03 7:41 ` K Lars Balker Rasmussen
1998-05-03 12:55 ` K Lars Magne Ingebrigtsen
1998-05-03 17:20 ` K Kim-Minh Kaplan
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=199805030312.UAA03482@mail1.teleport.com \
--to=flee@teleport.com \
--cc=ding@gnus.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 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).