From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin@cygwin.com
Subject: Re: Question regarding OpenSSL 1.1.1b package configuration against OpenSSL 1.0.2r
Date: Wed, 05 Jun 2019 03:04:00 -0000 [thread overview]
Message-ID: <05CCBA43-50CC-4B46-A707-27CAB735D348@solidrocksystems.com> (raw)
In-Reply-To: <5cf6f6fe.1c69fb81.9ba14.25bc@mx.google.com>
> On Jun 4, 2019, at 5:55 PM, Steven Penny wrote:
>
> Easy compared to what, assembly?
Easy compared to hard.
> He shows some domain knowledge of OpenSSL, but where are you getting that he
> knows about compiling C?
It's cygport, he doesn't have to know about compiling C. He has to know about
running a one-line cygport command.
>> Please refrain from your own inappropriate assumptions and meta-commentary
>> based on that, as this is not a social media platform.
>
> No, but it is a public forum. and I will call out nonsense if I see it. As your
> type of comments are off putting to new users.
Brian offered the user help. Brian is one of the most helpful people on this list. You
offered the user nothing, and berated Brian for offering help. The only nonsense on
offer here is from you. And the only one off-putting in this conversation is you.
--
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-06-05 3:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 12:09 Benjamin Baratte
2019-06-03 20:35 ` Brian Inglis
2019-06-03 22:36 ` Steven Penny
2019-06-04 14:32 ` Benjamin Baratte
2019-06-04 15:25 ` Brian Inglis
2019-06-04 22:56 ` Steven Penny
2019-06-05 3:04 ` Vince Rice [this message]
2019-06-05 4:12 ` Steven Penny
2019-06-05 4:26 ` Houder
2019-06-05 6:24 ` Brian Inglis
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=05CCBA43-50CC-4B46-A707-27CAB735D348@solidrocksystems.com \
--to=vrice@solidrocksystems.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).