From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Plan 9 annoyances
Date: Mon, 15 Oct 2001 14:28:41 +0900 [thread overview]
Message-ID: <20011015052715.CE4F3199BB@mail.cse.psu.edu> (raw)
This is a multi-part message in MIME format.
--upas-qycfbisqxumhebsxvegaqkrcpp
Content-Disposition: inline
Hmmm...
I'd made mistake to send previous mail.
Once again!, and see what will happen.
hehehe,
so ^[$B%"^[(Bis inputted through ktrans? :-)
Kenji
--upas-qycfbisqxumhebsxvegaqkrcpp
Content-Type: message/rfc822
Content-Disposition: inline
Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Mon Oct 15 13:56:44 JST 2001
Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2])
by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id NAA03751;
Mon, 15 Oct 2001 13:57:44 +0900
Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6])
by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-01090713) with ESMTP id NAA16671;
Mon, 15 Oct 2001 13:58:32 +0900 (JST)
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 56FE819AA8; Mon, 15 Oct 2001 00:58:11 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.101.69])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id A0A0719A0D
for <9fans@cse.psu.edu>; Mon, 15 Oct 2001 00:57:57 -0400 (EDT)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Plan 9 annoyances
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
From: okamoto@granite.cias.osakafu-u.ac.jp
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="upas-unjycyvowazednaswnwigrpoll"
Message-Id: <20011015045757.A0A0719A0D@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.6
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Mon, 15 Oct 2001 13:59:22 +0900
This is a multi-part message in MIME format.
--upas-unjycyvowazednaswnwigrpoll
Content-Disposition: inline
hehehe,
so ^[$B%"^[(B is inputted through ktrans? :-)
Kenji
--upas-unjycyvowazednaswnwigrpoll
Content-Type: message/rfc822
Content-Disposition: inline
Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Mon Oct 15 13:21:50 JST 2001
Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2])
by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id NAA03668;
Mon, 15 Oct 2001 13:22:50 +0900
Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6])
by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-01090713) with ESMTP id NAA16231;
Mon, 15 Oct 2001 13:23:34 +0900 (JST)
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 77BE419AA7; Mon, 15 Oct 2001 00:23:11 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from cosym.net (peter.sys.9srv.net [64.7.3.116])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 8C8CE19A19
for <9fans@cse.psu.edu>; Mon, 15 Oct 2001 00:22:44 -0400 (EDT)
To: 9fans@cse.psu.edu
From: anothy@cosym.net
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20011015042244.8C8CE19A19@mail.cse.psu.edu>
Subject: [9fans] Re: Plan 9 annoyances
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.6
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Mon, 15 Oct 2001 00:21:53 -0400
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by granite.cias.osakafu-u.ac.jp id NAA03668
// i see no real reason for "mk nuke" to exist.
i find there to be a useful distinction between these two:
"blow away all the intermediate files generated from a mk here"
"blow away _everything_ generated from a mk here"
i generally don't want 'mk clean' to blow away 8.out (although it does
in some places), but it's useful to have a command to get back to a
"pristine" state.
having 'mk nuke' blow away an installed libap.a does seem wrong,
although the building of libraries is sort of odd. i'd still be inclined =
to
change that.
=E3=82=A2 (i recently got ktrans working - thanks kenji - and am very
excited about it!)
--upas-unjycyvowazednaswnwigrpoll--
--upas-qycfbisqxumhebsxvegaqkrcpp--
next reply other threads:[~2001-10-15 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 5:28 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-15 5:44 okamoto
2001-10-15 4:59 okamoto
2001-10-15 4:21 anothy
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=20011015052715.CE4F3199BB@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).