From: Joel Brobecker <brobecker@adacore.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10 branching - 2020-06-27 Update
Date: Wed, 1 Jul 2020 14:21:04 -0700 [thread overview]
Message-ID: <20200701212104.GF5340@adacore.com> (raw)
In-Reply-To: <ydd4kqr9bzm.fsf@CeBiTec.Uni-Bielefeld.DE>
> it would be nice to get
>
> [PATCH] Unify Solaris procfs and largefile handling
> https://sourceware.org/pipermail/gdb-patches/2020-June/169977.html
>
> into GDB 10 which unbreaks the 32-bit GDB build on Solaris. Nick
> already approved the binutils parts of the patch; the gdb side is pretty
> much mechanical.
Sounds good to me, Rainer. Thanks for pointing it out.
--
Joel
next prev parent reply other threads:[~2020-07-01 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 15:40 Joel Brobecker
2020-07-01 21:11 ` Rainer Orth
2020-07-01 21:21 ` Joel Brobecker [this message]
2020-07-02 21:49 ` Simon Marchi
2020-07-03 15:10 ` Joel Brobecker
2020-07-03 15:12 ` Simon Marchi
2020-07-10 23:07 ` Pedro Alves
2020-07-03 0:35 ` Simon Marchi
2020-07-03 7:30 ` Eli Zaretskii
2020-07-03 15:06 ` Joel Brobecker
2020-07-03 15:15 ` Simon Marchi
2020-07-03 8:15 ` Sebastian Huber
2020-07-03 13:07 ` Andrew Burgess
2020-07-03 15:07 ` Joel Brobecker
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=20200701212104.GF5340@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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