From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] molesting the acme filesystem
Date: Fri, 14 Jul 2006 10:46:32 -0600 [thread overview]
Message-ID: <20060714104547.B1785@orthanc.ca> (raw)
In-Reply-To: <4f99d25e2af2ef50218a5846cfff0f7f@quanstro.net>
On Fri, 14 Jul 2006, quanstro@quanstro.net wrote:
> i'm not sure why acme and other plan9 filesystems typically disallow a trailing newline
> on input and don't provide one on output.
Yup. This one is my top entry for the confusomatic contest.
next prev parent reply other threads:[~2006-07-14 16:46 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 [this message]
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
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=20060714104547.B1785@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).