From: "Russ Cox" <rsc@mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sources changes
Date: Thu, 18 Sep 2003 09:03:26 -0400 [thread overview]
Message-ID: <dcc0ce9c24b52e608c14e816c20e5941@plan9.bell-labs.com> (raw)
In-Reply-To: <b6d8dd3a8d06a571526b3cfdd0bee770@collyer.net>
> Roughly 150 files have just been pushed out to sources.
> Could somebody at the labs summarise the changes?
A summer's worth of us falling behind.
Nothing major. New features documented.
Almost all of it well soaked.
Russ
next prev parent reply other threads:[~2003-09-18 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:17 Geoff Collyer
2003-09-18 13:03 ` Russ Cox [this message]
2003-09-18 13:24 ` 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=dcc0ce9c24b52e608c14e816c20e5941@plan9.bell-labs.com \
--to=rsc@mit.edu \
--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).