From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: info: x86: prev@6.1-2, x86_64: prev@6.3-1
Date: Mon, 03 Jul 2017 12:20:00 -0000 [thread overview]
Message-ID: <c0b3d80c-984e-3ab7-11c8-6276293a992d@cornell.edu> (raw)
In-Reply-To: <cf8e7cb58df14bc18de7fbbfcb6a780f@xs4all.nl>
On 7/3/2017 4:23 AM, Houder wrote:
> Ken,
>
> Noticed a difference where I did not expect one ...
>
> Oversight OR on purpose?
>
> prev of info in x86 is at 6.1-2, while it is at 6.3-1 in x86_64
I have no idea how that happened, but it should be fixed now. (It will
take an hour or so for the fix to reach the mirrors.)
Thanks for the report.
Ken
--
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:[~2017-07-03 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 8:23 Houder
2017-07-03 12:20 ` Ken Brown [this message]
2017-07-04 12:11 ` Houder
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=c0b3d80c-984e-3ab7-11c8-6276293a992d@cornell.edu \
--to=kbrown@cornell.edu \
--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).