From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10 branching - 2020-07-03 Update
Date: Fri, 03 Jul 2020 20:15:07 +0200 [thread overview]
Message-ID: <yddimf48nys.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20200703175710.GA10485@adacore.com> (Joel Brobecker's message of "Fri, 3 Jul 2020 10:57:10 -0700")
Hi Joel,
> Added Since the Last Update:
> ----------------------------
>
> * [RainerO]
> Unify Solaris procfs and largefile handling
> https://sourceware.org/pipermail/gdb-patches/2020-June/169977.html
>
> Seems to require a fair amount of coordination. binutils seems
> on board; what about GCC (for the part in config/)?
while largefile.m4 lives in the GCC tree, it isn't used anywhere. I'll
thus have to sync the file back once it's landed in binutils-gdb, but
that's it.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2020-07-03 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 17:57 Joel Brobecker
2020-07-03 18:15 ` Rainer Orth [this message]
2020-07-06 21:18 ` Sandra Loosemore
2020-07-07 0:44 ` Sandra Loosemore
2020-07-07 22:54 ` Kevin Buettner
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=yddimf48nys.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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