From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] FAQ
Date: Fri, 5 Apr 2002 13:15:49 -0500 [thread overview]
Message-ID: <23DFAA462CC6A64487613B0E242D9FF706EBFF@mercury.phoenix-interactive.com> (raw)
Well, to be fair that FAQ is getting a little threadbare.
Both lists seem to be getting a lot of repeated questions which aren't
addressed in the current FAQ. If someone wants to spend time contributing
then maybe that would cut down the volume on the lists.
Sean
-----Original Message-----
From: Geert Bevin [mailto:gbevin@uwyn.com]
Sent: Friday, April 05, 2002 1:42 AM
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] FAQ
I'm sorry, but this seems to be a user level faq right here :
http://www.gentoo.org/doc/faq.html
On Fri, 2002-04-05 at 01:48, Glen Redden wrote:
> I have used Gentoo for the last three months.
> I have noticed that the user list has been growing exponentially in the
> number of posts.
> I am finding it more and more difficult to find the time to sift through
the
> list.
> I expect many others out there who could provide the needed assistance
> cannot.
> The main thing that I have noticed about gentoo web site is the lack of a
> user level faq.
> I would like to create one.
> I have been studying the guide-xml and it makes doc writing much easier.
> I have also written a perl script that scours the user-list archive and
> creates a XML faq page.
> Of course some hand editing is required.
>
> To summarize:
> I would like to create/maintain a user-level faq page for gentoo linux.
> The page will reside on gentoo's site.
> Content of the page will focus on the gentoo distribution.
> Off site links to documentation will also be provided where the question
is
> more general to linux.
next reply other threads:[~2002-04-05 20:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 18:15 Sean Mitchell [this message]
2002-04-05 18:27 ` [gentoo-dev] FAQ Bjarke Sørensen
2002-04-05 20:02 ` George Shapovalov
2002-04-06 0:05 ` [gentoo-dev] FAQ submissions George Shapovalov
2002-04-05 13:07 ` [gentoo-dev] Issue with the gentoo.org website? Sherman Boyd
2002-04-06 1:23 ` Jano Lukac
2002-04-05 13:54 ` Sherman Boyd
2002-04-05 13:56 ` Sherman Boyd
-- strict thread matches above, loose matches on Subject: below --
2002-04-06 4:49 [gentoo-dev] FAQ Glen Redden
2002-04-06 7:27 ` George Shapovalov
2002-04-05 22:44 ` Dan Armak
2002-04-06 19:30 ` Erik Grinaker
2002-04-06 19:44 ` Erik Grinaker
2002-04-07 4:29 ` George Shapovalov
2002-04-07 12:45 ` Erik Grinaker
2002-04-07 15:14 ` Spider
2002-04-06 8:14 ` Bjarke Sørensen
2002-04-08 19:17 ` Thilo Bangert
2002-04-08 19:39 ` Erik Grinaker
2002-04-08 19:59 ` Thilo Bangert
2002-04-08 20:22 ` Erik Grinaker
2002-04-08 20:28 ` Erik Grinaker
2002-04-08 20:47 ` Michael Frank
2002-04-08 21:40 ` Thilo Bangert
2002-04-09 0:27 ` Kain
2002-04-08 20:05 ` Michael Lang
2002-04-08 20:32 ` Erik Grinaker
2002-04-08 21:43 ` George Shapovalov
[not found] <20020405200404.D8AFE20F0D8C@chiba.3jane.net>
2002-04-05 19:17 ` Glen Redden
[not found] <20020404232306.D13FE20F0B2D@chiba.3jane.net>
2002-04-04 23:48 ` Glen Redden
2002-04-05 6:41 ` Geert Bevin
2001-09-10 8:44 Djamil ESSAISSI
2001-09-10 8:57 ` Einar Karttunen
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=23DFAA462CC6A64487613B0E242D9FF706EBFF@mercury.phoenix-interactive.com \
--to=smitchell@phoenix-interactive.com \
--cc=gentoo-dev@gentoo.org \
/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