From: Ken Raeburn <raeburn@cygnus.com>
To: gas2@cygnus.com
Subject: weekly diff problem; other lameness on my part
Date: Thu, 18 Aug 1994 11:40:00 -0000 [thread overview]
Message-ID: <9408181837.AA00599@> (raw)
As Eric pointed out to me, the weekly diffs generated this week are too
short. Apparently, "diff" failed trying to read a file. Yet another
fix for my snapshot script...
Anyways, I haven't been keeping around past weeks' snapshots, so I can't
regenerate the correct set of weekly diffs. I'd suggest getting a new
snapshot, or getting the dailies since 940810 (the last weekly).
You may have noticed that some of the patches, bug reports &c you've
been sending to me might not've gotten dealt with as quickly as you
might like. Well, the network connection between me and the CVS source
repository has been pretty lame; in this case, it appears that both
Sprint and the Little Garden are hosed. Having been spoiled in previous
jobs by excellent network connectivity to anything that mattered, I've
been finding it frustrating to work under such conditions. So I've been
ignoring gas and concentrating on fixing our remote-cvs hack to function
better under these circumstances. This work should be finished shortly,
and I'll be getting back to doing assembler work.
(Yes, Ian does work in the same office and has still been getting things
done. I guess he's a bit more tolerant or disciplined than I am. :-)
reply other threads:[~1994-08-18 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9408181837.AA00599@ \
--to=raeburn@cygnus.com \
--cc=gas2@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).