public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Raphael <raphael@oninet.pt>
Cc: cygwin@cygwin.com
Subject: Re: FYI: HTML targets in "Smart Questions"
Date: Mon, 22 Jul 2002 13:18:00 -0000	[thread overview]
Message-ID: <Pine.CYG.4.44.0207221953060.376-100000@toos> (raw)
In-Reply-To: <001901c23101$c8457a40$0100a8c0@wdg.uk.ibm.com>

On Sun, 21 Jul 2002, Max Bowsher wrote:

> Jelks Cabaniss wrote:
> > Raphael wrote:
> >
> >> ... split the list in a 'dummies' and a 'BOFH' version ....
> >> The split is IMHO long overdue anyway, half of what I read
> >> is giberish to me anyway (yup put me in with the 'dummies')
> >> and resigning the list because of this has come to mind
> >> several times.
> >
> > I couldn't agree more.  That way we can read and learn from the posts
> > from the 'smart/experienced' folks on *this* list, and ask questions
> > on the 'dummies/newbies' list without being harangued by various
> > RTFM's, STFW's, pointers to etiquette screeds, etc.
>
> Although this may sound like a good idea at first though, I really don't
> see how it can work

It's quite easy actually, just as I take the time to instruct newbees that
there linelength is not according to current RFC´s other people might
point out cygwin newbees to FAQ's quoting the answer from a FAQ pointed
to. This encouridges people to read the faq instead of feeling harrashed.
And yes this happens on a lot of newbee lists becouse people do not expect
anything from them and exept the same question ask 100 times before they
start publishing a sort of weekly or montly FAQ, that is not appreciated
by the god who will then vanish to a god list. Easy.

> - the only questions which really generate RTFMs and
> haranguing are the truly dumb ones (that don't actually include enough
> information to give anyone a hope of answering correctly)

I always learned that the only dumb question is one that hasn't been
asked.

> , and the ones
> which have already been asked and answered in the past fortnight or so.

Thank you for your opinion, I hope you don't feel offended if it stay's
your and will not become mine.

> I agree that the traffic on this list can be absurdly high, but I think
> that is an unavoidable artefact of the large Cygwin user base.

Not if these kind of meta discussions a starting to become frequent. Noise
generates noise as this example quit clearly shows.

>
> Max.
>

Sorry for my English I probably missed a FAQ.

Raphael


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-07-22 19:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 16:17 Dario Alcocer
2002-07-20 11:34 ` Christopher Faylor
2002-07-20 11:48   ` Dario Alcocer
2002-07-21 14:40     ` Raphael
2002-07-21 14:59       ` Jelks Cabaniss
2002-07-21 16:26         ` Max Bowsher
2002-07-22 13:18           ` Raphael [this message]
2002-07-21 20:57       ` Dario Alcocer
2002-07-21 21:30         ` Jim Balcom
2002-07-21 23:04           ` Christopher Faylor
2002-07-22  1:09           ` Dario Alcocer
2002-07-22 13:08           ` Raphael
2002-07-22 13:32             ` Nicholas Wourms
2002-07-23  9:21               ` Larry Hall (RFK Partners, Inc)
2002-07-22 13:14         ` Raphael
2002-07-23 10:05           ` Dario Alcocer
2002-07-23 13:47             ` Raphael
2002-07-23 15:32               ` Jim George
2002-07-25 18:54                 ` Raphael
2002-07-21 21:21 Dockeen
2002-07-22  1:39 ` Dario Alcocer
2002-07-22 12:57   ` Raphael
2002-07-22 13:20 ` Raphael
2002-07-22 13:42 Dr. Wayne Keen

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.CYG.4.44.0207221953060.376-100000@toos \
    --to=raphael@oninet.pt \
    --cc=cygwin@cygwin.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).