9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Experiences with remote connections?
Date: Sat, 16 Jun 2007 13:42:02 -0600	[thread overview]
Message-ID: <14ec7b180706161242h6fca562cg5e6760f3ccfcd75a@mail.gmail.com> (raw)
In-Reply-To: <20070616193156.327001E8C22@holo.morphisms.net>

cfs can be a problem for a programmer: compile/run/debug/compile
cycles tend to be unfavourably long since everything has to be copied
back to the server and then read again.


  parent reply	other threads:[~2007-06-16 19:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 12:41 john
2007-06-16 18:59 ` Russ Cox
2007-06-16 13:11   ` john
2007-06-16 19:31     ` Russ Cox
2007-06-16 15:27       ` john
2007-06-16 19:42       ` andrey mirtchovski [this message]
2007-06-16 20:28         ` geoff
2007-06-16 22:12   ` Francisco J Ballesteros
2007-06-16 20:18 erik quanstrom

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=14ec7b180706161242h6fca562cg5e6760f3ccfcd75a@mail.gmail.com \
    --to=mirtchovski@gmail.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).