9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] [Heads-Up] Plan 9 Changes Emails
Date: Wed, 11 Apr 2007 23:29:35 -0400	[thread overview]
Message-ID: <9ab217670704112029r5d59ee87r5cb1917c33150c4b@mail.gmail.com> (raw)

Hi all,

As some of you may be aware, some time ago, Uriel created some scripts
to monitor sources, and send emails to a mailing list when changes
were made. During a portion of that time, Russ also spent some time
annotating changes to the Plan 9 source tree. He stopped when it
started taking too much time.

In a recent thread, Russ posted the script he had used to generate
diffs. It runs rather quickly for me and I've been spending the last
couple of days annotating changes. I've had to annoy Geoff a couple of
times about his changes, but I feel like it has been productive and a
good thing. I've been able to make a couple of suggestions (and learn
a bit about the system myself), so it's a good practice and a good
project.

I just wanted to let people know where these changes can be found,
since it has been about a year since they've been maintained. You can
see changes starting at 2007-04-07 in /n/sources/extra/changes/2007.
Changesets are mailed daily via a script Uriel provides. These go to
the 9changes mailing list, which you can sign up for and view at
http://groups.google.com/group/plan9changes

It doesn't take up too much of my time, and hasn't been too much of a
stress, so I hope to be able to continue this project for some time.

Hope this is useful for some people.

Kind regards,

Devon H. O'Dell


                 reply	other threads:[~2007-04-12  3:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9ab217670704112029r5d59ee87r5cb1917c33150c4b@mail.gmail.com \
    --to=devon.odell@gmail.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).