From: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: GDB 12.0.90 available for testing
Date: Thu, 7 Apr 2022 12:11:23 -0700 [thread overview]
Message-ID: <Yk83W4ruSJQSCpVu@adacore.com> (raw)
In-Reply-To: <87k0c090o0.fsf@tromey.com>
Hi Tom,
> I've got a patch.
>
> I'm not sure I can really send it to the list. It's quite large and
> it's nearly all mechanical, except the appended.
>
> I built & regtested it on x86-64 Fedora 34.
> I also used the Fedora mingw cross toolchain to do a mingw build.
>
> Tom
>
> diff --git a/gnulib/update-gnulib.sh b/gnulib/update-gnulib.sh
> index e4a910ff6c5..6025290deb3 100755
> --- a/gnulib/update-gnulib.sh
> +++ b/gnulib/update-gnulib.sh
> @@ -84,7 +84,7 @@ IMPORTED_GNULIB_MODULES="\
> "
>
> # The gnulib commit ID to use for the update.
> -GNULIB_COMMIT_SHA1="776af40e09b476a41073131a90022572f448c189"
> +GNULIB_COMMIT_SHA1="58c597d13bc57dce3e97ea97856573f2d68ccb8c"
>
> # The expected version number for the various auto tools we will
> # use after the import.
Is it just code, or does this update also cause the imports to
somehow change? The import changes would be the only thing that
might raise red-flags for me. Other than that, I don't think
I'd need to see the diff, really. The import process being
automated IIRC, it's all mechanical, as you say.
--
Joel
next prev parent reply other threads:[~2022-04-07 19:12 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 5:58 Joel Brobecker via Gdb-patches
2022-03-26 15:26 ` Eli Zaretskii via Gdb-patches
2022-03-26 15:53 ` Joel Brobecker via Gdb-patches
2022-03-26 16:15 ` Eli Zaretskii via Gdb-patches
2022-04-07 16:08 ` Tom Tromey
2022-04-07 16:12 ` Eli Zaretskii via Gdb-patches
2022-04-07 18:00 ` Joel Brobecker via Gdb-patches
2022-04-07 18:04 ` Simon Marchi via Gdb-patches
2022-04-07 19:02 ` Tom Tromey
2022-04-07 19:11 ` Joel Brobecker via Gdb-patches [this message]
2022-04-08 13:38 ` Tom Tromey
2022-04-08 14:33 ` Pedro Alves
2022-04-18 15:26 ` Tom Tromey via Gdb-patches
2022-04-18 16:13 ` Tom Tromey via Gdb-patches
2022-04-07 18:30 ` Tom Tromey
2022-04-08 6:58 ` Eli Zaretskii via Gdb-patches
2022-04-18 19:28 ` Tom Tromey via Gdb-patches
2022-03-26 17:59 ` Eli Zaretskii via Gdb-patches
2022-03-26 18:34 ` Eli Zaretskii via Gdb-patches
2022-03-26 18:51 ` Eli Zaretskii via Gdb-patches
2022-03-27 6:27 ` Eli Zaretskii via Gdb-patches
2022-03-31 6:23 ` Eli Zaretskii via Gdb-patches
2022-03-31 9:48 ` Pedro Alves
2022-03-31 11:55 ` Eli Zaretskii via Gdb-patches
2022-04-01 10:12 ` Andrew Burgess via Gdb-patches
2022-04-01 11:18 ` Eli Zaretskii via Gdb-patches
2022-04-01 11:25 ` Eli Zaretskii via Gdb-patches
2022-04-01 15:21 ` Andrew Burgess via Gdb-patches
2022-04-01 16:18 ` Eli Zaretskii via Gdb-patches
2022-04-03 13:02 ` Hannes Domani via Gdb-patches
2022-04-03 13:34 ` Eli Zaretskii via Gdb-patches
2022-04-03 14:03 ` Joel Brobecker via Gdb-patches
2022-04-03 15:26 ` Hannes Domani via Gdb-patches
2022-04-03 15:38 ` Eli Zaretskii via Gdb-patches
2022-04-07 11:09 ` Eli Zaretskii via Gdb-patches
2022-04-07 18:03 ` Joel Brobecker via Gdb-patches
2022-04-10 19:06 ` Joel Brobecker via Gdb-patches
2022-04-11 11:42 ` Eli Zaretskii via Gdb-patches
2022-04-17 17:28 ` Joel Brobecker via Gdb-patches
2022-04-19 16:12 ` Andrew Burgess via Gdb-patches
2022-04-19 16:16 ` Eli Zaretskii via Gdb-patches
2022-04-20 13:26 ` Andrew Burgess via Gdb-patches
2022-04-20 17:11 ` Joel Brobecker via Gdb-patches
2022-04-20 17:30 ` Eli Zaretskii via Gdb-patches
2022-04-24 15:56 ` Joel Brobecker via Gdb-patches
2022-04-25 8:48 ` Andrew Burgess via Gdb-patches
2022-04-07 18:28 ` Tom Tromey via Gdb-patches
2022-04-07 19:22 ` Pedro Alves
2022-04-08 4:04 ` Eli Zaretskii via Gdb-patches
2022-04-01 12:36 ` Joel Brobecker via Gdb-patches
2022-04-01 12:50 ` Eli Zaretskii via Gdb-patches
2022-04-01 14:12 ` Joel Brobecker via Gdb-patches
2022-04-01 14:27 ` Eli Zaretskii via Gdb-patches
2022-04-01 14:31 ` Joel Brobecker via Gdb-patches
2022-04-08 14:44 ` Pedro Alves
2022-04-08 20:05 ` Eli Zaretskii via Gdb-patches
2022-03-27 9:55 ` Eli Zaretskii via Gdb-patches
2022-03-27 1:55 ` Simon Marchi via Gdb-patches
2022-03-27 5:20 ` Eli Zaretskii via Gdb-patches
2022-04-07 16:13 ` Tom Tromey
2022-04-07 16:39 ` Eli Zaretskii via Gdb-patches
2022-03-31 6:21 ` Eli Zaretskii via Gdb-patches
2022-03-31 9:44 ` Pedro Alves
2022-03-31 11:58 ` Eli Zaretskii via Gdb-patches
2022-03-31 12:05 ` Pedro Alves
2022-03-31 14:00 ` Eli Zaretskii via Gdb-patches
2022-04-12 14:01 ` Luis Machado via Gdb-patches
2022-04-12 17:57 ` Joel Brobecker via Gdb-patches
2022-04-13 7:36 ` Luis Machado via Gdb-patches
2022-04-13 12:19 ` Luis Machado via Gdb-patches
2022-04-13 16:20 ` Jose E. Marchesi via Gdb-patches
2022-04-17 17:33 ` Joel Brobecker via Gdb-patches
2022-04-18 1:48 ` Alan Modra via Gdb-patches
2022-04-26 13:54 ` Luis Machado via Gdb-patches
2022-04-26 14:56 ` Joel Brobecker via Gdb-patches
2022-04-26 15:15 ` Luis Machado via Gdb-patches
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52 ` Joel Brobecker via Gdb-patches
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=Yk83W4ruSJQSCpVu@adacore.com \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=tom@tromey.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