9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] to-do list for plan 9
Date: Mon, 28 Apr 2003 23:58:34 +0200	[thread overview]
Message-ID: <c1999cd427eb143482393964e486e184@plan9.escet.urjc.es> (raw)

Hi
	while talking to Russ I noticed that it would be
nice to have a shared to-do list for Plan 9. For example,
I'd perhaps work on making the system suspend/resume on the laptop,
arranging the boot process to use fossil when installing from CD, etc.
Many times I dont start something because I think that someone in the
labs is working on it.

Thus, what about sharing our personal plan 9 to-do lists using, eg, the
wiki, and updating them to record who's working on what?

Now that I talk about a related issue, I still have the fs redirection
stuff which needs just a bit of work to get a production version able
to fail down from a remote file server to a local kfs, fossil or whatever.
Is there any interest on this? That may change its possition in my todo
list.

hope this helps (and hope also this does not end up in an endless
9fans thread with no practical result ;-).



             reply	other threads:[~2003-04-28 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28 21:58 Fco.J.Ballesteros [this message]
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
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=c1999cd427eb143482393964e486e184@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).