This is the mail archive of the
mailing list for the GDB project.
Re: [PING][PATCH] Fix amd64->i386 linux syscall restart problem
- From: Kevin Buettner <kevinb at redhat dot com>
- To: Tom de Vries <tdevries at suse dot de>
- Cc: gdb-patches at sourceware dot org, Pedro Alves <palves at redhat dot com>
- Date: Mon, 8 Jul 2019 10:00:01 -0700
- Subject: Re: [PING][PATCH] Fix amd64->i386 linux syscall restart problem
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On Fri, 21 Jun 2019 08:34:46 +0200
Tom de Vries <firstname.lastname@example.org> wrote:
> On 21-05-19 14:59, Tom de Vries wrote:
> > On 11-04-19 02:16, Kevin Buettner wrote:
> >> On Wed, 10 Apr 2019 12:42:30 +0100
> >> Pedro Alves <email@example.com> wrote:
> >>>> Below is a diff showing the new comments. It also includes the
> >>>> changes which wrap the multi-line expressions in parens.
> >>> Thanks, that new version of the comment looks great.
> >> It's in now. Thanks for the review.
> > Hi,
> > the tests fixed by this commit fail on the 8.3 branch (filed as PR24592).
> > The commit applies cleanly on the 8.3 branch, and make the tests pass.
> > OK to backport?
> [ Ping. ]
> I'm probably missing some context here. It seems sofar there are no
> commits to the 8.3 branch. AFAIU, a respin release 8.3.1 is targeted for
> 3 months after 8.3, so around 11th of August.
> What kind of fixes are acceptable for the respin? Do they have to be
> regression fixes? Or are functionality fixes like this one also allowed?
> Who's responsibility is it to backport fixes?
> - Tom
I'm okay with it going into the next point release for 8.3.