From: Kevin Buettner <kevinb@redhat.com>
To: 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 17:39:00 -0000 [thread overview]
Message-ID: <20180910103940.5c623c9e@pinnacle.lan> (raw)
In-Reply-To: <20180910171205.18594-1-sergiodj@redhat.com>
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.
Kevin
next prev parent reply other threads:[~2018-09-10 17:39 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 ` Kevin Buettner [this message]
2018-09-10 17:55 ` [PATCH 0/2] Revert gnulib update and backport gnulib fix for PR gdb/23558 Sergio Durigan Junior
2018-09-10 18:14 ` Tom Tromey
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=20180910103940.5c623c9e@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/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