From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bind, ns weirdness
Date: Thu, 6 Mar 2003 17:51:25 -0500 [thread overview]
Message-ID: <ebc80bfd9d9bf5dab474ef1f2bc488e7@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.SOL.3.96.1030306202406.2863B-100000@robin.cooper.edu>
no, the name should remain unchanged.
if the name changes at all in the ns listing
then there's no point in keeping them around.
the whole point of the suggestion was to
make the ns file effectively append-only,
so it shows a valid history.
russ
next prev parent reply other threads:[~2003-03-06 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 1:32 Joel Salomon
2003-03-06 22:51 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 23:52 Keith Nash
2003-03-06 21:18 ` Russ Cox
2003-03-06 21:58 Keith Nash
2003-03-06 22:16 ` David Presotto
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=ebc80bfd9d9bf5dab474ef1f2bc488e7@plan9.bell-labs.com \
--to=rsc@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).