From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: The selective fire-at command
Date: Wed, 18 Aug 2004 00:48:00 -0000 [thread overview]
Message-ID: <l03130303bd48471ecdc1@[212.181.162.155]> (raw)
In-Reply-To: <Pine.LNX.4.44.0408171910030.419-100000@leon.phy.cmich.edu>
>out. Also, as you pointed out, the attack command and
>corresponding action did work as advertized, and so it cannot be
>claimed that those who advocated it were using it under a
>delusion in the way that I was using fire under a delusion.
Indeed, and as I also stated I can appreciate the potential usefulness of
both commands, even if I rarely use them myself. Keeping them is on my
revised agenda, and I am even trying to fix the tcltk fire-at command so
that it finally will work.
Hans
next prev parent reply other threads:[~2004-08-17 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 22:15 Hans Ronne
2004-08-17 22:59 ` Eric McDonald
2004-08-17 23:25 ` Hans Ronne
2004-08-17 23:36 ` Eric McDonald
2004-08-18 0:48 ` Hans Ronne [this message]
2004-08-18 3:00 ` Eric McDonald
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='l03130303bd48471ecdc1@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=mcdonald@phy.cmich.edu \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).