From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] lots of binaries
Date: Wed, 27 Nov 2002 21:33:07 -0500 [thread overview]
Message-ID: <73a283234a7a7cd269f2733c511615d1@plan9.bell-labs.com> (raw)
When you do your next pull, every binary
on your system will be updated.
(You can also use the "bleeding edge" update CD on
the updates web page, after it gets regenerated
tomorrow morning at 5am EST; it's probably
less to download.)
The binaries all changed because hardly any of
them had been recompiled since the fmt library
fixes (posted on October 18 to 9fans) went in.
Going forward, we will be running "mk release"
for every architecture every night, both to make
sure that everything builds and to catch binaries
that are out of date.
Russ
next reply other threads:[~2002-11-28 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 2:33 Russ Cox [this message]
2002-12-03 9:06 Ian Dichkovsky
2002-12-03 13:51 Russ Cox
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=73a283234a7a7cd269f2733c511615d1@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).