From: "Ernest Clayton Cordell, Jr." <ErnieC@ix.netcom.com>
To: "'Michael Hirmke'" <mh@mike.franken.de>
Cc: "'gnu-win32@cygnus.com'" <gnu-win32@cygnus.com>
Subject: RE: splitting this list ?
Date: Sat, 27 Sep 1997 12:21:00 -0000 [thread overview]
Message-ID: <01BCCB58.F0F54E20@rvl-md7-22.ix.netcom.com> (raw)
I think your idea is good in concept, but since I'm not the one who has to
do the work, I defer judgement to those who more directly hold a stake in
maintaining this list.
Rather than receiving a FAQ on joining, I would suggest a 'FAQ letter' that
explains that there are resources available to those who are using this
"environment" for
Installation -- Inst URLs
Builds -- make/compile/install URLs
programming -- pertinent URLs
ports -- some people are interested in "successful ports," others in
"details to port" (maybe Build/maybe Install)?
but each FAQ really only pertains to the version; while I'm several
versions and releases behind, I still find the most recent FAQ useful by
virtue of the items it has included over time. "Newbies" (in usage of
Cygwin tools, rather than in DP/whatever experience) may not realize that
the FAQ at "latest" may refer to problems/solutions that don't apply to
their particular version/release.
I think it would help to mention such things in the subscription
confirmation message: The caveat that people may be too busy to answer
questions or that 'you have asked a question that is already in a FAQ,'
endlessly clarified things for me.
The group of inexperienced 'users' (rather than developers) who received
disks from SAMS publishing (or some such source) are really left without a
clue. They need help, but I'm not sure this list is appropriate; since
SAMS publishing sends them to this list in the first place, maybe it would
be appropriate to send them back to the SAMS publishing page.
Maybe it would help to include the topics "flame messages," "product
slurring," and just plain "venting."
Ernie
----------
From: Michael Hirmke
Sent: Saturday, September 27, 1997 8:33 AM
To: gnu-win32@cygnus.com
Subject: splitting this list ?
Hi *,
just a thought - would anybody support splitting up this list into lets
say "installing", "programming" and "porting" lists ?
It seems, that more and more people use Cygnus' gcc and therefore
especially the installation issues will grow in number the next months.
We already see many questions regarding installation topics in here.
Second idea - it would be great, if anyone joining this list would get
a FAQ, which mentions the most common problems during installation and
configuration !
Any comments ?
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://minimike.franken.de/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-09-27 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-27 12:21 Ernest Clayton Cordell, Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-30 9:57 Earnie Boyd
1997-09-29 21:17 Ernest Clayton Cordell, Jr.
1997-09-29 18:59 Earnie Boyd
1997-09-28 9:10 Wouter Schaart
1997-09-30 8:19 ` mdevos
1997-09-27 6:53 Michael Hirmke
1997-09-27 16:36 ` Tibor Polgar
1997-10-05 16:39 ` Winona Strater
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=01BCCB58.F0F54E20@rvl-md7-22.ix.netcom.com \
--to=erniec@ix.netcom.com \
--cc=gnu-win32@cygnus.com \
--cc=mh@mike.franken.de \
/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).