From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: [PATCH 1/2] Revert "Update gnulib to current upstream master"
Date: Mon, 10 Sep 2018 17:17:00 -0000 [thread overview]
Message-ID: <87va7dqnkr.fsf@redhat.com> (raw)
In-Reply-To: <20180910171205.18594-1-sergiodj@redhat.com> (Sergio Durigan Junior's message of "Mon, 10 Sep 2018 13:12:03 -0400")
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Monday, September 10 2018, I 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.
I forgot that sourceware has a size limit for e-mails, so the first one
bounced. Here it is, compressed.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
[-- Attachment #2: 0001-Revert-Update-gnulib-to-current-upstream-master.patch.gz --]
[-- Type: application/gzip, Size: 255146 bytes --]
next prev parent reply other threads:[~2018-09-10 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 17:12 [PATCH 0/2] Revert gnulib update and backport gnulib fix for PR gdb/23558 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 ` Sergio Durigan Junior [this message]
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
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=87va7dqnkr.fsf@redhat.com \
--to=sergiodj@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