Re: GDB 8.3.1 to be released very soon!

[Tom de Vries <tdevries@suse.de>]

On 20-09-19 17:20, Joel Brobecker wrote:
>>> As far as I know, there is only one patch series that's pending
>>> confirmation that it's OK to backport:
>>>
>>>   * [TomDV] Add Rust support to source highlighting
>>>     https://www.sourceware.org/ml/gdb-patches/2019-09/msg00225.html
>>>
>>>     The backport of the second patch needs confirmation that
>>>     it's OK (TomT). Please remember that all patches going into
>>>     the .1 need to have a corresponding PR, with the PR's target
>>>     milestone being set to 8.3.1, so TomDV will need to adjust
>>>     his patches accordingly.
>>>
>>
>> This is done.
> 
> Thanks for confirming. I missed that when I sent you a private note
> a few minutes ago about it...
> 
>>> If anyone has other changes that are pending for 8.3.1, now is
>>> the time to say so; unless there are more patches, I'm planning
>>> on creating the release on Friday or Saturday.
>>>
>>
>> I've only got one outstanding patch for 8.3, which adds a KFAIL, not a
>> gdb code change, so not strictly necessary and more of a convenience.
>> This is "[PATCH, 8.3][gdb/testsuite] Mark watchthreads-reorder.exp FAIL
>> as KFAIL" @ https://sourceware.org/ml/gdb-patches/2019-09/msg00221.html .
> 
> If it was just me deciding, I would keep it out. It's only for developers
> where it's not really going to make such a difference, since we tend to
> validate patches by diffing the results before and after, while at
> the same time, it's using a central function of our testsuite. It's
> a fairly mechanical change, so the risk is probably relatively low,
> but even then, I don't think the gains are worth that risk.
> 

Hi Joel,

I'm fine with going by your guidance and skipping this patch. I don't
want the release to be held up for this.

Thanks,
- Tom