From: Russ Allbery <rra@cs.stanford.edu>
Subject: Re: 5.2.25 problems with courtesy copy
Date: 23 Jun 1996 03:54:29 -0700 [thread overview]
Message-ID: <qumrar6pz8a.thoron@cyclone.Stanford.EDU> (raw)
In-Reply-To: Russ Allbery's message of 23 Jun 1996 02:29:10 -0700
Russ Allbery <rra@CS.Stanford.EDU> writes:
> Overall, that was one of the most painful upgrades I have ever had to go
> through, and I don't ever want to do that again. I like the new
> features, [...]
Actually, after a negative message and calming down, I should repeat
that. I *like* the new features. I wish the upgrade were smoother, but
there is a *lot* to like about the new version and upgrading was
definitely worth it.
--
Russ Allbery (rra@cs.stanford.edu) <URL:http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~1996-06-23 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-23 9:29 Russ Allbery
1996-06-23 10:54 ` Russ Allbery [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=qumrar6pz8a.thoron@cyclone.Stanford.EDU \
--to=rra@cs.stanford.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).