From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: GDB 10 branching - 2020-06-27 Update
Date: Fri, 3 Jul 2020 08:06:54 -0700 [thread overview]
Message-ID: <20200703150654.GJ5340@adacore.com> (raw)
In-Reply-To: <0b1b1404-d383-42de-1e7a-fca1a6df0a2d@simark.ca>
> Another item would be the Guile 2.2 and 3.0 support, the latest version
> being here:
>
> https://sourceware.org/pipermail/gdb-patches/2020-June/169936.html
>
> It's been a quite long-running issue:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=21104
>
> and it's nice to finally have someone address it. It would be a shame
> I think if it didn't make it into this release.
I'll follow the group on that one. It's a risk vs reward situation:
How risky is it for us to put the patch in just before the branch,
versus how much do we expect to gain by having it now rather than
in 6 months? Given that this should only affect Guile support,
I suppose the risk we are taking is limited to that part. If the risk
is low and acceptable to everyone, then we can decide to have it
in GDB 10. I'll put it on the list for now...
> I have looked at the patches, but I know nothing about this, so I can't
> review them properly. Do you know who would be most qualified to review
> this?
Traditionally, it's been Doug Evans.
--
Joel
next prev parent reply other threads:[~2020-07-03 15:06 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
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 [this message]
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=20200703150654.GJ5340@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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).