From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Revert gnulib update and backport gnulib fix for PR gdb/23558
Date: Mon, 10 Sep 2018 18:14:00 -0000 [thread overview]
Message-ID: <87o9d5rzj7.fsf@tromey.com> (raw)
In-Reply-To: <87lg89qlth.fsf@redhat.com> (Sergio Durigan Junior's message of "Mon, 10 Sep 2018 13:55:22 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> On Monday, September 10 2018, Kevin Buettner wrote:
>> On Mon, 10 Sep 2018 13:12:03 -0400
>> Sergio Durigan Junior <sergiodj@redhat.com> wrote:
>>
>>> This patch series finally fixes the problem introduced by the gnulib
>>> update. It's a simple series: the first patch totally reverts the
>>> update, and the second patch just cherry-picks the fix for PR
>>> gdb/23558 from gnulib master.
>>
>> This is okay.
Sergio> Thanks, pushed:
Sergio> e2fc52e745757a11f7a4a256984cabbe5474f55a
Sergio> 5e8754f90abbbf832987477eea4ee91a9d2f694c
Thanks for doing this.
If you're not planning to work on fixing the gnulib
compiler-flag-choosing thing soon, could you file a gdb bug with some
links to the various threads, so that we have an easy way to refer
back to them?
Tom
next prev parent reply other threads:[~2018-09-10 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 17:12 Sergio Durigan Junior
2018-09-10 17:12 ` [PATCH 2/2] Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB Sergio Durigan Junior
2018-09-10 17:17 ` [PATCH 1/2] Revert "Update gnulib to current upstream master" Sergio Durigan Junior
2018-09-10 17:39 ` [PATCH 0/2] Revert gnulib update and backport gnulib fix for PR gdb/23558 Kevin Buettner
2018-09-10 17:55 ` Sergio Durigan Junior
2018-09-10 18:14 ` Tom Tromey [this message]
2018-09-10 18:24 ` Sergio Durigan Junior
2018-09-12 22:42 ` Sergio Durigan Junior
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=87o9d5rzj7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=sergiodj@redhat.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