From: matt@juice.thebigchoice.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Building a cpu/auth server
Date: Mon, 7 Jun 2004 16:27:33 +0100 [thread overview]
Message-ID: <cfe81255950bd1f8d07107026416be74@juice.thebigchoice.com> (raw)
In-Reply-To: <ee9e417a040607074144853657@mail.gmail.com>
I see what you mean about the first bind. I dont use that way anyway
wrt the other binds : just doing what Rob advised
that way if you do a replica and a file changes in /sys/src your copied version wont get out of step *and* you know which files you have changed just by ls, if they aren't there, you haven't changed them. Easier than walking the whole tree with diff
but, hey, whatever works for you
m
prev parent reply other threads:[~2004-06-07 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 14:01 Frank Palazzolo
2004-06-07 14:16 ` matt
2004-06-07 14:41 ` Russ Cox
2004-06-07 15:27 ` matt [this message]
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=cfe81255950bd1f8d07107026416be74@juice.thebigchoice.com \
--to=matt@juice.thebigchoice.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).