From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jan Nieuwenhuizen <janneke@gnu.org>, Simon Marchi <simark@simark.ca>
Cc: gdb@sourceware.org
Subject: Re: [PATCH 3/3] gdb: More compile fixes for gnu-nat.c.
Date: Mon, 22 Nov 2021 21:35:50 -0500 [thread overview]
Message-ID: <128e167c-ea32-6fe8-3dd6-410186bee3bd@polymtl.ca> (raw)
In-Reply-To: <87a6hw56yt.fsf@gnu.org>
On 2021-11-22 14:24, Jan Nieuwenhuizen via Gdb wrote:
> Simon Marchi writes:
>
> Hello Simon,
>
>> I only see patch 3/3, is it normal? Otherwise, patches should be sent
>> to the gdb-patches mailing list (same address, just with gdb-patches
>> instead of gdb).
>
> Ah, oops. Yeah, I was using two other patches on top of gdb-11-branch;
> one by you, cherry-pickef from master, and one sent to this list. I'm
> attaching them for completeness. Yes, I can send my patch to
> gdb-patches if that's helpful.
Ok, thanks. We missed patch 2/3, I found it on the list and pushed it
to git master. I then applied and pushed yours as well, thanks.
Simon
prev parent reply other threads:[~2021-11-23 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 7:30 Jan (janneke) Nieuwenhuizen
2021-11-22 15:17 ` Simon Marchi
2021-11-22 19:24 ` Jan Nieuwenhuizen
2021-11-23 2:35 ` Simon Marchi [this message]
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=128e167c-ea32-6fe8-3dd6-410186bee3bd@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=janneke@gnu.org \
--cc=simark@simark.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).