From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Sam commands in acme
Date: Mon, 29 Jun 2009 18:03:28 +0100 [thread overview]
Message-ID: <df49a7370906291003k23196d14tfed6ca5aae728fad@mail.gmail.com> (raw)
In-Reply-To: <7359f0490906271220q4773f616k7d1a6ec79a3a30bc@mail.gmail.com>
2009/6/27 Rob Pike <robpike@gmail.com>:
> Deletion is the greatest tool of software design.
yes, i always get great pleasure from deleting code.
unfortunately the overall line count almost always seems to trend
upwards regardless of the amount of code deleted.
next prev parent reply other threads:[~2009-06-29 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 9:50 hugo rivera
2009-06-26 10:42 ` yy
2009-06-26 11:54 ` hugo rivera
2009-06-26 12:05 ` Rudolf Sykora
2009-06-26 12:21 ` hugo rivera
2009-06-26 10:57 ` roger peppe
2009-06-27 18:17 ` J.R. Mauro
2009-06-27 19:20 ` Rob Pike
2009-06-27 20:32 ` J.R. Mauro
2009-06-29 17:03 ` roger peppe [this message]
2009-06-29 17:20 ` erik quanstrom
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=df49a7370906291003k23196d14tfed6ca5aae728fad@mail.gmail.com \
--to=rogpeppe@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).