From: "Harri Haataja" <realblades@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] dc(1) questions
Date: Tue, 15 Apr 2008 23:28:49 +0300 [thread overview]
Message-ID: <74e3492a0804151328k1c0fd147rea7202d75aa09bac@mail.gmail.com> (raw)
In-Reply-To: <20080415135135.GA7847@dinah>
On 15/04/2008, Anthony Martin <ality@pbrane.org> wrote:
> 3. Is it wrong to love bc(1) for being a compiler? ;)
In my opinion, absolutely not. I wish more software was.
<3
--
I appear to be temporarily using gmail's horrible interface. I
apologise for any failure in my part in trying to make it do the right
thing with post formatting.
prev parent reply other threads:[~2008-04-15 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 13:51 Anthony Martin
2008-04-15 20:28 ` Harri Haataja [this message]
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=74e3492a0804151328k1c0fd147rea7202d75aa09bac@mail.gmail.com \
--to=realblades@gmail.com \
--cc=9fans@9fans.net \
/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).