9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] to-do list for plan 9
Date: Tue, 29 Apr 2003 11:39:58 -0400	[thread overview]
Message-ID: <Pine.LNX.4.30.0304291108510.11411-100000@athena> (raw)
In-Reply-To: <Pine.LNX.4.44.0304290844450.3977-100000@maxroach.lanl.gov>

>
> good idea, but how do we get kernel mods in. Also, I'd like to show people
> my (very minor) mods and get comments. Does that fit the plan?
>

The most direct way to this end seems to be collecting the
files you've changed into a set of directories with a
script to bind them in as appropriate before compilation.

A todo list is a nice idea, especially if it encourages
people to participate.  Perhaps it would be more aptly
characterized with a list of work-in-progress and a list
of proposed work, though.

Either way you're assuming the barrier others
face in announcing the projects they're tinkering with
is that this list doesn't already exist.  I somehow
think it has more to do with the fact that ``if you
announce it, they will harrass you.''  The best avenue
for discovering whether someone is working on a project
you're considering still seems to be a quick poke to
9fans.

Creating such a list for one's own personal projects
may not be a bad idea and is a jolly good use of the wiki. :)

Cheers,

Sam




  parent reply	other threads:[~2003-04-29 15:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28 21:58 Fco.J.Ballesteros
2003-04-29 14:49 ` ron minnich
2003-04-29 14:55   ` Russ Cox
2003-04-29 16:29     ` Christopher Nielsen
2003-04-29 15:39   ` Sam [this message]
2003-04-29 15:56     ` andrey mirtchovski
2003-04-29 16:12     ` ron minnich
2003-04-29 16:35     ` Christopher Nielsen
2003-04-30  7:58       ` Fco.J.Ballesteros
2003-04-29 16:28   ` Christopher Nielsen
2003-04-29 16:26 ` Christopher Nielsen
2003-04-30  0:02 ` Boyd Roberts
2003-04-30  0:26   ` ron minnich
2003-04-30  0:41     ` Boyd Roberts

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=Pine.LNX.4.30.0304291108510.11411-100000@athena \
    --to=sah@softcardsystems.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).