From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] $sysname isn't set in the 'live' part of the iso
Date: Thu, 17 May 2007 12:41:52 +0200 [thread overview]
Message-ID: <ba0d3bc70705170341j3b4f4956i6ab079b8dc53be24@mail.gmail.com> (raw)
In-Reply-To: <20070517092801.GA2910@crazypenguin.whypasp.net>
On 5/17/07, David JEANNOT <djeannot24@gmail.com> wrote:
> See "sorry: termrc-error" on plan9changes list for the fix.
> Indeed, It doesn't seem to have been applied yet.
Considering it was sorried, I doubt it's going to be applied. I guess
it was deemed an incorrect fix. I lack knowledge to judge whether this
is right or wrong, but regardless of that, the original problem is
still there.
Greetings, Sander.
next prev parent reply other threads:[~2007-05-17 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 7:30 Sander van Dijk
2007-05-17 9:28 ` David JEANNOT
2007-05-17 10:41 ` Sander van Dijk [this message]
2007-05-21 7:42 ` Sergey Zhilkin
2007-05-21 9:35 ` Sander van Dijk
2007-05-21 11:25 ` Richard Miller
2007-05-22 10:04 ` Sander van Dijk
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=ba0d3bc70705170341j3b4f4956i6ab079b8dc53be24@mail.gmail.com \
--to=a.h.vandijk@gmail.com \
--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).