From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What the reason of much change of rc(1)
Date: Thu, 17 Jul 2003 10:37:08 -0400 [thread overview]
Message-ID: <6af263ecf0dd5c8acd58afb98cf074ff@plan9.bell-labs.com> (raw)
In-Reply-To: <b7a88f7100cd508c482096dba21ab4de@granite.cias.osakafu-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
I did indeed reformat it. I was making a version that would work
both on windows and unix/plan9 and got angry at the formating style.
The have{nt}fork.c was indeed for os's without fork.
[-- Attachment #2: Type: message/rfc822, Size: 2192 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What the reason of much change of rc(1)
Date: Thu, 17 Jul 2003 10:38:55 +0900
Message-ID: <b7a88f7100cd508c482096dba21ab4de@granite.cias.osakafu-u.ac.jp>
> I noticed today, so much of the sources of /sys/src/cmd/rc
> have been changed recently.
> Why?
I reexamined it this morning, and found most changes are
only for coding style or habit ☺ except of adding a file of
havefork.c. Probably for generalization of codes for various
operating systems...
Then, now, I'm convinced rc(1) has not been changed. ☺
Kenji
next prev parent reply other threads:[~2003-07-17 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 7:38 okamoto
2003-07-17 1:38 ` okamoto
2003-07-17 14:37 ` David Presotto [this message]
2003-07-17 15:17 ` Philippe Anel
2003-07-17 16:54 ` boyd, rounin
2003-07-17 16:14 ` Scott Schwartz
2003-07-17 16:51 ` rog
2003-07-17 17:38 ` boyd, rounin
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=6af263ecf0dd5c8acd58afb98cf074ff@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).