From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica (was: ipv6)
Date: Tue, 28 May 2002 17:42:08 +0100 [thread overview]
Message-ID: <20020528164945.26274199B6@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
inconsistencies arise at a different level too:
i noticed that the lookupcmd code appeared throughout ip(v4)
only to vanish again just now!
[-- Attachment #2: Type: message/rfc822, Size: 4537 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 26 bytes --]
I'm pretty sure you don't.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 2898 bytes --]
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica (was: ipv6)
Date: Tue, 28 May 2002 15:26:22 +0200
Message-ID: <200205281326.g4SDQMx27511@zamenhof.cs.utwente.nl>
> I moved our ipv4+6 stack onto sources.cs.bell-labs.com.
Your message arrived here while I had replica/pull running.
I don't know whether this already came up in the replica
discussion so far... (or can be R in TFM):
if you push while I'm pulling, do I still get
a 'consistent' set of files?
Axel.
next reply other threads:[~2002-05-28 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 16:42 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 22:19 rsc
2002-05-28 23:33 ` Micah Stetson
2002-05-28 21:28 rsc
2002-05-28 21:55 ` Chris Hollis-Locke
2002-05-28 20:58 presotto
2002-05-28 16:55 rsc
2002-05-28 15:35 Russ Cox
2002-05-28 16:41 ` postmaster
2002-05-28 15:32 Russ Cox
2002-05-28 15:05 presotto
2002-05-28 12:29 [9fans] ipv6 presotto
2002-05-28 13:26 ` [9fans] replica (was: ipv6) 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=20020528164945.26274199B6@mail.cse.psu.edu \
--to=forsyth@vitanuova.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).