From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] beware sources for a few days
Date: Wed, 30 Aug 2006 22:39:53 -0400 [thread overview]
Message-ID: <18ea0ac84f16ae876c70f2e9d0954a19@plan9.bell-labs.com> (raw)
In-Reply-To: <51f3c0134e143f002d413451e16fe408@plan9.bell-labs.com>
The sources update and build machinery seems to be working again.
I've done a replica/scan and generated fresh new ISO images. The Plan
9 one does seem to be a little over 79MB compressed.
I've reenabled the cron jobs and we'll see what happens overnight.
As always, a pull -n before a real pull is a wise precaution.
prev parent reply other threads:[~2006-08-31 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 6:36 geoff
2006-08-31 2:39 ` geoff [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=18ea0ac84f16ae876c70f2e9d0954a19@plan9.bell-labs.com \
--to=geoff@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).