From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Jonah Graham <jonah@kichwacoders.com>,
Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, dje.gcc@gmail.com
Subject: Re: Proposal to revert the gnulib update patch
Date: Tue, 04 Sep 2018 18:09:00 -0000 [thread overview]
Message-ID: <87tvn5xhhc.fsf@tromey.com> (raw)
In-Reply-To: <87y3ciytr7.fsf_-_@redhat.com> (Sergio Durigan Junior's message of "Mon, 03 Sep 2018 20:46:20 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> Since the main reason for updating gnulib was to fix PR gdb/23558, as a
Sergio> workaround, I propose that we backport just the upstream gnulib patch
Sergio> that fixes the problem:
Sergio> a96d2e67052c879b1bcc5bc461722beac75fc372
Sergio> I'd like to hear your opinions.
I think this would be fine.
We don't want to be permanently stuck on an old gnulib, but on the other
hand there's plenty of time in the next cycle to fix this. Meanwhile
your proposal would unbreak things for people.
One thing that would be good would be to file a bug documenting what's
needed, with links and such. In the past tasks like this have gotten
"lost" -- information being theoretically available in the archives
somewhere, but in practice very hard to find.
Tom
next prev parent reply other threads:[~2018-09-04 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:31 Oh dear. I regret to inform you that commit 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 might be unfortunate gdb-buildbot
2018-08-29 16:31 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 gdb-buildbot
2018-08-29 16:39 ` Sergio Durigan Junior
2018-08-29 20:42 ` Sergio Durigan Junior
2018-08-29 21:33 ` Tom Tromey
2018-08-29 21:37 ` Sergio Durigan Junior
2018-08-30 0:50 ` Tom Tromey
2018-08-30 3:04 ` Sergio Durigan Junior
2018-09-01 0:01 ` Tom Tromey
2018-09-03 10:04 ` Jonah Graham
2018-09-04 0:46 ` Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24) Sergio Durigan Junior
2018-09-04 6:20 ` Jonah Graham
2018-09-04 18:04 ` Proposal to revert the gnulib update patch Sergio Durigan Junior
2018-09-04 18:09 ` Tom Tromey [this message]
2018-08-30 3:06 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 Sergio Durigan Junior
2018-08-30 1:55 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2018-08-30 1:57 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-08-30 1:58 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
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=87tvn5xhhc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jonah@kichwacoders.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).