From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: mteege@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] looking for a new plan 9 faq maintainer
Date: Thu, 21 Oct 2004 14:40:17 +0200 [thread overview]
Message-ID: <c64aade83f8d2468eaf64071de8a5262@plan9.escet.urjc.es> (raw)
In-Reply-To: <88a4775604102104457811e569@mail.gmail.com>
> On Thu, 21 Oct 2004 13:44:29 -0400, andrey kukhar <plan9@kp.km.ua> wrote:
>> If you'd like to take over the faq maintenance, please
>> email me directly.
>
> I'm interessted on this job.
>
>> You'll need to be able to host it on your own site.
> no problem
>
> Matthias
I'd suggest to change `faq maintainer' with `wiki maintaner'.
I mean, the wiki was meant to be the faq. It's out of date
because many of us forget to update it. Instead of
maintaining a separate thing, why not maintain the wiki?
hth
next prev parent reply other threads:[~2004-10-21 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 17:44 andrey kukhar
2004-10-21 11:45 ` Matthias Teege
2004-10-21 12:40 ` Fco. J. Ballesteros [this message]
[not found] ` <20041021134633.GA5351@ns.0xfe.org>
2004-10-22 17:25 ` andrey kukhar
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=c64aade83f8d2468eaf64071de8a5262@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
--cc=mteege@gmail.com \
/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).