From: "Dockeen" <dockeen@mchsi.com>
To: <cygwin@cygwin.com>
Subject: RE: Setup as recommended reading
Date: Sun, 26 May 2002 09:05:00 -0000 [thread overview]
Message-ID: <NCBBLKKJGBJOLDFMCKFPIEGICAAA.dockeen@mchsi.com> (raw)
There is a motivation in my recommendation that
goes beyond what's new.
A few months ago, in a discussion with a new user,
he pointed out that as his needs and requirements
evolved, and he needed something he wasn't using
previously in Cygwin, he was suprised at how often,
he found, like the commercial says "its in there".
and...
How often are there posts from users who "thought
they installed everything", only to have to be told
to go back and open category x and install what they
wanted.
I'm probably weird, but I don't see a problem with
respect to how setup works in this respect.
Wayne Keen
p.s. I am still also pushing the notion of the archives
as an at least daily read. If I keep learning at this
rate, in a few decades, I might even be able to contribute!
--
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/
next reply other threads:[~2002-05-26 4:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 9:05 Dockeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 2:01 Robert Collins
2002-05-26 13:47 Robert Collins
2002-05-26 18:19 ` Nicholas Wourms
2002-05-26 12:11 Robert Collins
2002-05-26 8:59 Robert Collins
2002-05-26 11:57 ` Brian Gallew
2002-05-26 12:13 ` René Møller Fonseca
2002-05-26 6:30 Robert Collins
[not found] <30C9E24891FFD411B68A009027724CB74433DD@eg-002-015.eglin.af .mil>
2002-05-22 11:55 ` Larry Hall (RFK Partners, Inc)
2002-05-22 9:31 Keen Wayne A Contr AFRL/MNGG
2002-05-26 0:55 ` Jim.George
[not found] ` <Pine.CYG.4.44.0205251652540.1876-100000@gateway.GEORGE.CO. UK>
2002-05-26 0:58 ` Larry Hall (RFK Partners, Inc)
2002-05-26 5:20 ` Christopher Faylor
2002-05-27 6:24 ` Jim.George
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=NCBBLKKJGBJOLDFMCKFPIEGICAAA.dockeen@mchsi.com \
--to=dockeen@mchsi.com \
--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).