From: Jose Isaias Cabrera <jicman@outlook.com>
To: Erik Soderquist <erik.soderquist@gmail.com>, cygwin <cygwin@cygwin.com>
Subject: Re: Is our use of Cygwin to build & run OpenOCD a good one?
Date: Mon, 20 May 2019 14:27:00 -0000 [thread overview]
Message-ID: <DB7PR01MB5386F37F1AA9DE324DF60E8EDE060@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CACoZoo1Q=DyY0i-SFHjGmU8BeJgGCkTEfkYXJ32QGF63BxSoZQ@mail.gmail.com>
Erik Soderquist, on Monday, May 20, 2019 10:16 AM, wrote...
>On Sun, May 19, 2019 at 3:44 PM Bob Cochran wrote:
><snip>
>> "Cygwin? this is probably still functional, but now can be considered a
>> (pre)historic solution."
>
>The words of the ignorant, in my opinion. Cygwin has done an
>excellent job of maintaining currency and usefulness.
Indeed. I have been using cygwin since 1996-7. Can't remember the exact year, but it has been God-sent, and it has been in every Windows machine I have had control. Just my 0.02. Thanks.
josé
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-05-20 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 19:44 Bob Cochran
2019-05-19 20:53 ` LRN
2019-05-19 21:21 ` Brian Inglis
2019-05-20 14:16 ` Erik Soderquist
2019-05-20 14:27 ` Jose Isaias Cabrera [this message]
2019-05-20 18:49 ` Bob Cochran
2019-05-21 17:55 ` LRN
2019-05-21 18:21 ` Jose Isaias Cabrera
2019-05-22 6:05 ` Bob Cochran
2019-05-22 21:35 ` Andrey Repin
2019-05-23 1:47 ` Brian Inglis
2019-05-23 1:52 ` Brian Inglis
2019-05-23 1:55 ` Brian Inglis
2019-05-20 17:54 ` Achim Gratz
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=DB7PR01MB5386F37F1AA9DE324DF60E8EDE060@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=erik.soderquist@gmail.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).