This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: time to create the GDB 8.1.x branch?


> > 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]