From: Sam Steingold <sds@gnu.org>
To: Robert Collins <rbcollins@cygwin.com>
Cc: cygwin@cygwin.com
Subject: Re: setup.hint / ldesc
Date: Fri, 05 Sep 2003 21:42:00 -0000 [thread overview]
Message-ID: <u4qzq3obb.fsf@gnu.org> (raw)
In-Reply-To: <1062797241.744.2.camel@localhost>
> * In message <1062797241.744.2.camel@localhost>
> * On the subject of "Re: setup.hint / ldesc"
> * Sent on Sat, 06 Sep 2003 07:27:21 +1000
> * Honorable Robert Collins <rbcollins@cygwin.com> writes:
>
> On Sat, 2003-09-06 at 05:33, Sam Steingold wrote:
>
> > > The description of the setup.ini/setup.hint "language" at
> > > http://cygwin.com/setup.html is accurate.
> >
> > any plans to add something like that?
> > E.g., is a field starts with $, pass it to the shell...
> >
> > ldesc is not used at this time, so, I guess, I will just leave it blank :-)
>
> Whats so hard in just following the recipe provided?
why should I maintain two identical texts in two separate files?
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
Those who don't know lisp are destined to reinvent it, poorly.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-09-05 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 16:45 Sam Steingold
2003-09-05 19:02 ` Christopher Faylor
2003-09-05 19:33 ` Sam Steingold
2003-09-05 19:46 ` Igor Pechtchanski
2003-09-05 20:46 ` Christopher Faylor
2003-09-05 21:27 ` Robert Collins
2003-09-05 21:42 ` Sam Steingold [this message]
2003-09-07 10:26 ` Hannu E K Nevalainen (garbage mail)
2003-09-07 17:40 ` Sam Steingold
2003-09-07 18:07 ` Christopher Faylor
2003-09-07 18:23 ` Christopher Faylor
2003-09-05 19:07 ` Igor Pechtchanski
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=u4qzq3obb.fsf@gnu.org \
--to=sds@gnu.org \
--cc=cygwin@cygwin.com \
--cc=rbcollins@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).