From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Christian Biesinger <cbiesinger@google.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDBserver ports cleanup
Date: Wed, 13 May 2020 16:01:38 +0100 [thread overview]
Message-ID: <820c0734-3c9c-5d69-57f1-8de81b82de36@redhat.com> (raw)
In-Reply-To: <dbf19fb1-20e6-a98d-7239-10baa1a5b6ad@polymtl.ca>
On 5/13/20 3:45 PM, Simon Marchi wrote:
> Thanks for the storytelling, I enjoyed it :).
>
:-)
> If removing support for WinCE ends up simplifying win32-low.cc, it is a net gain,
> since that file is used today.
Yes, and removing all that should make it easier to continue the effort to merging
gdb's windows-nat.c and gdbserver's win32-low.cc.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-05-13 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:47 Simon Marchi
2020-05-12 20:26 ` Christian Biesinger
2020-05-13 12:01 ` Pedro Alves
2020-05-13 14:45 ` Simon Marchi
2020-05-13 15:01 ` Pedro Alves [this message]
2020-05-13 12:37 ` Luis Machado
2020-05-13 13:11 ` Alan Hayward
2020-05-13 14:47 ` Simon Marchi
2020-05-13 18:36 ` Joseph Myers
2020-05-13 18:40 ` Simon Marchi
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=820c0734-3c9c-5d69-57f1-8de81b82de36@redhat.com \
--to=palves@redhat.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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