From: David Swasey <swasey@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] current environment?
Date: Thu, 13 Feb 2003 16:06:39 -0500 [thread overview]
Message-ID: <913139431a4f81a8ec8306af32bab99f@cs.cmu.edu> (raw)
In-Reply-To: <200302131843.h1DIhHL04178@highwire.stanford.edu>
I have a linux box on my LAN that holds code for other systems. I
work in acme, using u9fs+p9any for editing, ssh+make for batch
compiles, and win+ssh for interactive work. (The SML/NJ compilation
manager recompiles faster when used interactively.)
A nightly cron job does replica/scan && replica/pull to copy changes
from my linux box to my file server so the dump gets a copy of my
source. This is very handy.
I sometimes have to work with remote machines over a slow link. I use
unison to propagate changes between my linux box and these machines
and VNC+whatever for editing
-dave
> Anyone in a similar
> position w/re to writing code which won't be running on a Plan 9 box?
> What do you do?
prev parent reply other threads:[~2003-02-13 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 18:43 James A. Robinson
2003-02-13 18:47 ` William Josephson
2003-02-13 18:48 ` Russ Cox
2003-02-13 19:26 ` matt
2003-02-13 21:06 ` David Swasey [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=913139431a4f81a8ec8306af32bab99f@cs.cmu.edu \
--to=swasey@cs.cmu.edu \
--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).