From: <tlake@twcny.rr.com>
To: <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] Updated: Cygwin 2.11.0-1
Date: Sun, 02 Sep 2018 09:22:00 -0000 [thread overview]
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAABQRSoLbf9Qompmb9LgUCAAQAAAAA=@twcny.rr.com> (raw)
In-Reply-To: <315b0989-33bd-9e03-be70-eeb013cb0a91@cornell.edu>
On 9/1/2018 2:52 PM, tlake@twcny.rr.com wrote:
> Now I can't get 2.11.0-1. I tried over 20 mirrors and none of them have the update.
Are you sure you don't have it already? Try 'cygcheck -cd cygwin' to find out:
$ cygcheck -cd cygwin
Cygwin Package Information
Package Version
cygwin 2.11.0-1
Ken
Sure enough! That's what I have. I thought that since I installed Cygwin before the announcement that I would've had an earlier build.
Thanks, Ken! I'm learning something new about Cygwin every day. Eventually, I may become almost competent.
Now if only I could figure out how to compile a C program in Win 10 without a segmentation error...
Tom L
--
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-02 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ba47be31-bea8-6dbe-5672-8ff1def50e22@gmail.com>
2018-09-01 18:52 ` tlake
2018-09-01 21:57 ` Ken Brown
2018-09-02 9:22 ` tlake [this message]
[not found] <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADvnGgM5JZdRqTbz0tuc6XKAQAAAAA=@twcny.rr.com>
2018-09-01 18:48 ` tlake
2018-08-31 20:05 Corinna Vinschen
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=''\!'&'\!'AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAABQRSoLbf9Qompmb9LgUCAAQAAAAA=@twcny.rr.com' \
--to=tlake@twcny.rr.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).