From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Mon, 27 Nov 2017 22:14:00 -0000 [thread overview]
Message-ID: <20171127221413.2kry6ypqkqjzff6p@adacore.com> (raw)
In-Reply-To: <20171127220628.xdgwwvsrmrylw3go@adacore.com>
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00174.html
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00175.html
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00171.html
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00172.html
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00173.html
> > https://sourceware.org/ml/gdb-patches/2017-08/msg00176.html
> >
> > The GDB support needs the new regset provided by Linux kernel, so
> > these GDB patches can't go in until the kernel patches are merged.
> > I think kernel patches will be merged in several (5?) weeks, is it OK to
> > get these GDB patches into 8.1 release (mainline first and backport to
> > 8.1 branch)? To be clear, I don't expect GDB 8.1 release should be
> > delayed in case that kernel patches merge won't happen in several weeks.
> > The reason I ask this is that I want to make sure we are OK to merge
> > such new feature support to release branch.
BTW - something that could help me track the status of a patch
series like this one is if there was a GDB PR with a target milestone
of 8.1. That way, I don't have to track email messages by subject
or reference ID across multiple months; something we know the email
archives are not helping with. Instead, I just wait for the PR to move
to fixed. Would that be possible?
Thanks!
--
Joel
next prev parent reply other threads:[~2017-11-27 22:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55 ` Joel Brobecker
2017-11-28 19:44 ` Ulrich Weigand
2017-11-28 20:32 ` Pedro Alves
2017-11-29 13:20 ` Pedro Alves
2017-11-29 21:00 ` Joel Brobecker
2017-11-29 21:49 ` Pedro Alves
2017-11-29 22:20 ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves
2017-11-27 22:20 ` Joel Brobecker
2017-11-27 22:41 ` Pedro Alves
2017-11-29 20:56 ` Joel Brobecker
2017-11-29 22:20 ` Pedro Alves
2017-11-29 22:46 ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi
2017-11-27 22:06 ` Joel Brobecker
2017-11-27 22:14 ` Joel Brobecker [this message]
2017-11-28 12:38 ` Yao Qi
2017-11-29 20:58 ` Joel Brobecker
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23 ` Joel Brobecker
2017-11-28 17:08 ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50 ` Joel Brobecker
2017-11-23 17:32 ` Pedro Alves
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=20171127221413.2kry6ypqkqjzff6p@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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