From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipv6 missing in pc^(auth cd flop) on sources?
Date: Sat, 29 Jun 2002 10:34:27 -0400 [thread overview]
Message-ID: <598f0a81bc0dff83354f0db9433b91e5@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 120 bytes --]
Sorry about that. I just updated the conf's that were in the
CONFLIST in the mkfile. I should have looked for others.
[-- Attachment #2: Type: message/rfc822, Size: 2533 bytes --]
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] ipv6 missing in pc^(auth cd flop) on sources?
Date: Sat, 29 Jun 2002 16:27:59 +0200
Message-ID: <200206291428.g5TERxa18840@zamenhof.cs.utwente.nl>
I got the impressions not all pc* configurations had been updated...
(but the changes were easy enough to copy from (eg) pcdisk)
Axel.
next reply other threads:[~2002-06-29 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 14:34 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-29 14:27 Axel Belinfante
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=598f0a81bc0dff83354f0db9433b91e5@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.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).