From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] formatting the manual from plan9 ports?
Date: Wed, 30 May 2012 00:03:09 -0400 [thread overview]
Message-ID: <04891bb0d6c90b9ad927c933160a3df5@brasstown.quanstro.net> (raw)
In-Reply-To: <a7da0139aa96cc7db4ca3c14a688ed9c@rei2.9hal>
On Tue May 29 23:48:31 EDT 2012, cinap_lenrek@gmx.de wrote:
> short hardcoded paths are an advantage. this is not linux. this
> is plan9. there are rules. the kernel already provides a way for
> indirection that works for *everything*. mount/bind and private
> namespaces.
while this is all true, and i agree with you, the problem at hand it
to get things formatted on linux.
- erik
next prev parent reply other threads:[~2012-05-30 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 19:03 Aharon Robbins
2012-05-25 19:08 ` pmarin
2012-05-29 20:46 ` Aharon Robbins
2012-05-29 21:05 ` erik quanstrom
2012-05-30 3:44 ` cinap_lenrek
2012-05-30 4:03 ` erik quanstrom [this message]
2012-05-30 6:11 arnold
2012-05-30 12:38 ` 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=04891bb0d6c90b9ad927c933160a3df5@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).