From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] molesting the acme filesystem
Date: Fri, 14 Jul 2006 11:37:43 -0600 [thread overview]
Message-ID: <44B7D667.40804@lanl.gov> (raw)
In-Reply-To: <3e1162e60607141036h1e6f3455n77cb773cb981f333@mail.gmail.com>
David Leimbach wrote:
> some of them are clearly inserting newlines, like event and they
> require one as well to be a completed "event".
maybe I misunderstood if you're just talking acme.
But for the system as a whole, there are mnay places where a gratuitious
\n would add a lot of mess.
ron
next prev parent reply other threads:[~2006-07-14 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 1:24 David Leimbach
2006-07-14 2:54 ` quanstro
2006-07-14 5:12 ` David Leimbach
2006-07-14 12:07 ` quanstro
2006-07-14 16:46 ` Lyndon Nerenberg
2006-07-14 17:30 ` Ronald G Minnich
2006-07-14 17:29 ` quanstro
2006-07-14 17:48 ` Ronald G Minnich
2006-07-14 17:43 ` quanstro
2006-07-14 17:36 ` David Leimbach
2006-07-14 17:37 ` Ronald G Minnich [this message]
2006-07-14 17:33 ` quanstro
2006-07-14 17:44 ` David Leimbach
2006-07-14 17:35 ` David Leimbach
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=44B7D667.40804@lanl.gov \
--to=rminnich@lanl.gov \
--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).