From: "James A. Robinson" <jim.robinson@stanford.edu>
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] sam vs acme
Date: Thu, 19 Jul 2001 08:00:51 -0700 [thread overview]
Message-ID: <200107191500.f6JF0p117188@highwire.stanford.edu> (raw)
In-Reply-To: Message from steve.simon@snellwilcox.com of "Thu, 19 Jul 2001 12:39:19 BST."References: <3796700714@snellwilcox.com> <3796700714@snellwilcox.com>
> I only wish the Windows version understood sam -r...
Is it because of a lack of rsh? Because one of the things I do
with sam is tweak it to use ssh instead. I imagine the same could
be done easily enough with the windows version.
There isn't anything about the underlying structure of sam -r that
would fail under windows right? From what I remember of the book
Rob co-authored (Practice of Programming) they talk a lot about how
to get around things like endian problems.
Jim
next prev parent reply other threads:[~2001-07-19 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 11:39 steve.simon
2001-07-19 15:00 ` James A. Robinson [this message]
2001-07-19 22:21 ` Boyd Roberts
2001-07-19 22:09 ` Boyd Roberts
2001-07-19 14:45 Dan Cross
2001-07-19 14:56 ` Re[2]: " Matt
2001-07-19 15:24 rob pike
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=200107191500.f6JF0p117188@highwire.stanford.edu \
--to=jim.robinson@stanford.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).