From: Hans Zoebelein <zocki@goldfish.cube.net>
To: blinux-list@redhat.com
Cc: Charles Hallenbeck <2ndsight@taconic.net>,
Lar Kaufman <lark@world.std.com>
Subject: Blinux FAQ was Re: More on "man" and editors
Date: Sun, 20 Dec 1998 00:25:08 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.00.9812200018500.1356-100000@goldfish.cube.net> (raw)
In-Reply-To: <Pine.GSO.4.05.9812190139450.1039-100000@shell.clark.net>
Blinux really needs a Blinux FAQ.
Some questions shine up on a regular basis like
"Which is the best Linux distribution to use?".
A Blinux FAQ will improve information and reduce multiple postings.
Anybody out here who wants to write the Blinux FAQ?
Hans
On Sat, 19 Dec 1998, Jude Dashiell wrote:
> This list doesn't have a faq file yet. Those who would care to complain
> about basic questions being asked here are perfectly welcome to construct
> such a list and post it
> on this list regularly. That's standard operating procedure on other more
parent reply other threads:[~ UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.GSO.4.05.9812190139450.1039-100000@shell.clark.net>]
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.00.9812200018500.1356-100000@goldfish.cube.net \
--to=zocki@goldfish.cube.net \
--cc=2ndsight@taconic.net \
--cc=blinux-list@redhat.com \
--cc=lark@world.std.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 read-only IMAP folder(s) and NNTP newsgroup(s).