From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/3] Warning fixes for gcc 10.2
Date: Sun, 27 Sep 2020 12:04:24 -0600 [thread overview]
Message-ID: <f5291780-3a7e-9112-8178-2ef0edafc006@SystematicSw.ab.ca> (raw)
In-Reply-To: <1425a69b-d1a9-1479-4083-3839910352ee@cornell.edu>
On 2020-09-21 16:39, Ken Brown via Cygwin-patches wrote:
> On 9/21/2020 3:25 PM, Jon Turney wrote:
>> Jon Turney (3):
>> Cygwin: avoid GCC 10 error with -Werror=parentheses
>> Cygwin: avoid GCC 10 error with -Werror=narrowing
>> Cygwin: avoid GCC 10 error with -Werror=narrowing
>>
>> winsup/cygwin/fhandler_console.cc | 4 ++--
>> winsup/cygwin/fhandler_socket_inet.cc | 2 +-
>> winsup/cygwin/ntdll.h | 2 +-
>> winsup/cygwin/pseudo-reloc.cc | 2 --
>> 4 files changed, 4 insertions(+), 6 deletions(-)
>
> LGTM.
>
> Ken
Same or better than what I came up with, before I came on here to post, and saw
you had already dealt with those! ++PUSH
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-27 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 19:25 Jon Turney
2020-09-21 19:25 ` [PATCH 1/3] Cygwin: avoid GCC 10 error with -Werror=parentheses Jon Turney
2020-09-21 19:25 ` [PATCH 2/3] Cygwin: avoid GCC 10 error with -Werror=narrowing Jon Turney
2020-09-21 19:25 ` [PATCH 3/3] " Jon Turney
2020-09-21 22:39 ` [PATCH 0/3] Warning fixes for gcc 10.2 Ken Brown
2020-09-27 18:04 ` Brian Inglis [this message]
2020-09-30 3:30 ` 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=f5291780-3a7e-9112-8178-2ef0edafc006@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@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).