From: Richard Campbell <richard.u.campbell@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Curl
Date: Mon, 24 Sep 2018 21:32:00 -0000 [thread overview]
Message-ID: <CALwydEvocfDFcPxcwq5GQPN-G-dR09CJWEbrCUXeMYpcdytTGw@mail.gmail.com> (raw)
In-Reply-To: <11410442401.20180924224501@yandex.ru>
Over 300 bugfixes and 4 security vulnerabilities were fixed between
Curl 7.59 (most current cygwin, released in March) and Curl 7.61.1
(most current at curl.haxx.se, released September 5), if I'm reading
the Curl page correctly.
https://curl.haxx.se/docs/releases.html
https://cygwin.com/packages/x86_64/curl/
On Mon, Sep 24, 2018 at 2:50 PM Andrey Repin <anrdaemon@yandex.ru> wrote:
>
> Greetings, Mcclintock, Timothy M CTR USARMY MEDCOM JMLFDC (US)!
>
> > With the latest updates to OpenSSL will we be seeing a new version of Curl as well?
>
> What's wrong with current one?
>
>
> --
> With best regards,
> Andrey Repin
> Monday, September 24, 2018 22:43:45
>
> Sorry for my terrible english...
>
>
> --
> 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
>
--
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:[~2018-09-24 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 16:22 Curl Mcclintock, Timothy M CTR USARMY MEDCOM JMLFDC (US)
2018-09-24 19:50 ` Curl Andrey Repin
2018-09-24 21:32 ` Richard Campbell [this message]
2021-10-09 3:55 Curl Jeremy Luttrell
2021-11-26 14:47 Curl Richard Burce
2021-11-26 17:39 ` Curl 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=CALwydEvocfDFcPxcwq5GQPN-G-dR09CJWEbrCUXeMYpcdytTGw@mail.gmail.com \
--to=richard.u.campbell@gmail.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).