From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: alef compiler
Date: Tue, 25 May 2004 15:42:03 +0100 [thread overview]
Message-ID: <1886900bbb681ddab9ed9a36b0110649@vitanuova.com> (raw)
In-Reply-To: <EDA3C6D6-AE57-11D8-B24F-003065E1714E@corpus-callosum.com>
> deleted code is debugged code
one of the great things about the dump filesystem is the total
freedom to delete code. no need to keep it around "just in case":
it's available, but needn't clog things up.
next prev parent reply other threads:[~2004-05-25 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 18:01 [9fans] " Matthew Swank
2004-05-24 6:58 ` [9fans] " Russ Cox
2004-05-24 18:01 ` Matthew Swank
2004-05-24 23:04 ` Latchesar Ionkov
2004-05-24 23:24 ` Russ Cox
2004-05-25 1:53 ` boyd, rounin
2004-05-24 23:35 ` Matthew Swank
2004-05-25 0:42 ` rog
2004-05-25 14:29 ` Jeff Sickel
2004-05-25 14:42 ` rog [this message]
2004-05-25 17:51 ` boyd, rounin
2004-05-25 17:56 ` Fco. J. Ballesteros
2004-05-25 0:07 dmr
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=1886900bbb681ddab9ed9a36b0110649@vitanuova.com \
--to=rog@vitanuova.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).