From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new wrap
Date: Mon, 7 May 2001 18:43:21 +0100 [thread overview]
Message-ID: <E14wp2Z-0000bR-0X@anchor-post-33.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 72 bytes --]
I'd assumed it was to assist in the proper implementation of main().
[-- Attachment #2: Type: message/rfc822, Size: 1474 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new wrap
Date: Mon, 07 May 2001 13:41:19 -0400
Message-ID: <20010507174119.21095.qmail@g.bio.cse.psu.edu>
Dave writes:
| This is sort of like '#s' for segments, i.e., segments
| that can be attached by unrelated processes.
Can you say a few words about what inspired this, and how it's intended to
be used? Things in #s are always globally visible... ## too? It reminds
me of SysV shm.
next reply other threads:[~2001-05-07 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 17:43 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-07 17:57 presotto
2001-05-07 17:20 presotto
2001-05-07 17:41 ` Scott Schwartz
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=E14wp2Z-0000bR-0X@anchor-post-33.mail.demon.net \
--to=nigel@9fs.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).