9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] To upgrade or not to upgrade ...
Date: Thu, 31 May 2001 22:43:43 +0000	[thread overview]
Message-ID: <20010531224343.A389@localhostnl.demon.nl> (raw)

To upgrade or not to upgrade. That is the question.

Here is the output from my wrap/info plan9:

plan9 (full package as of Wed Jan 31 05:22:50 EST 2001)
pkg 964893367: Plan 9 from Bell Labs — Third Edition
pkgupd 971556349 updating 961264382: Plan 9 from Bell Labs — Third Edition
pkgupd 971810713 updating 971556349: Plan 9 from Bell Labs — Third Edition
pkgupd 980936570 updating 971556349: Plan 9 - wiki software

I know I have missed some upgrades lately but I noticed on
the list what I thought were some bugs with people that did
the upgrade.

Should I upgrade now or hold back? If I should, which
packages should I wrap/inst?

-- 
Bill                             William Staniewicz
                                 Amsterdam, NL


             reply	other threads:[~2001-05-31 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 22:43 William Staniewicz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31 21:03 forsyth

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=20010531224343.A389@localhostnl.demon.nl \
    --to=wstan@localhostnl.demon.nl \
    --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).