From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] p9p mk issue
Date: Thu, 22 Nov 2007 19:20:18 +0100 [thread overview]
Message-ID: <20071122182018.GA2724@shodan.homeunix.net> (raw)
In-Reply-To: <20071122174322.E07B55B3E@mail.bitblocks.com>
I think what Russ meant was to put all complicated stuff that uses rc syntax
into a separate file with MKSHELL=rc on top and include that in yor mkfiles
(cf. mkone/mkmany on Plan 9).
Martin
next prev parent reply other threads:[~2007-11-22 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 21:01 Bakul Shah
2007-11-20 21:08 ` Pietro Gagliardi
2007-11-20 21:44 ` Pietro Gagliardi
2007-11-20 22:20 ` Jeff Sickel
2007-11-20 22:48 ` Bakul Shah
2007-11-21 7:44 ` John Stalker
2007-11-21 16:01 ` Russ Cox
2007-11-21 18:01 ` Bakul Shah
2007-11-21 19:57 ` Pietro Gagliardi
2007-11-22 15:47 ` Russ Cox
2007-11-22 17:43 ` Bakul Shah
2007-11-22 18:20 ` Martin Neubauer [this message]
2007-11-22 19:48 ` Russ Cox
2007-11-30 18:01 ` Bakul Shah
2007-11-30 19:01 ` Russ Cox
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=20071122182018.GA2724@shodan.homeunix.net \
--to=m.ne@gmx.net \
--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).