public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Update gnulib to current upstream master
Date: Wed, 29 Aug 2018 16:29:00 -0000	[thread overview]
Message-ID: <87y3cpm90l.fsf@redhat.com> (raw)
In-Reply-To: <87zhx54043.fsf@tromey.com> (Tom Tromey's message of "Wed, 29 Aug	2018 10:18:52 -0600")

On Wednesday, August 29 2018, Tom Tromey wrote:

>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> It has been a while since we don't update our gnulib copy against
> Sergio> their upstream master branch, so I thought I'd propose this patch.  It
> Sergio> also fixes (at least) one bug reported against GDB:
> Sergio>   https://sourceware.org/bugzilla/show_bug.cgi?id=23558
>
> Thank you for doing this.
>
> I think it is ok.  It's an enormous auto-generated patch, so of course I
> didn't read it.  But I think this point in the release cycle is a good
> time to update gnulib, and worst case we can either (1) back this out,
> or (2) fix whatever gnulib bugs might arise.
>
> BTW you mentioned on irc that you forgot to mention update-gnulib.sh in
> the ChangeLog; please do that, no need to repost though.

Thanks, Tom.  I pushed the patch with the updated ChangeLog:

7a6dbc2fdb2323c35e981f93236f323e9d7c0b24

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

  reply	other threads:[~2018-08-29 16:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 19:59 Sergio Durigan Junior
2018-08-29 16:19 ` Tom Tromey
2018-08-29 16:29   ` Sergio Durigan Junior [this message]
2018-08-29 19:06 ` Pedro Alves
2018-08-29 19:34   ` Sergio Durigan Junior
2018-08-31 13:04     ` Pedro Alves
2018-08-30  0:04   ` Tom Tromey
2018-08-30  3:01     ` Sergio Durigan Junior
2018-08-30 15:57   ` [PATCH] Update gnulib/Makefile.in:aclocal_m4_deps Sergio Durigan Junior
2018-08-30 17:05     ` Simon Marchi
2018-08-30 20:00       ` Sergio Durigan Junior
2018-08-31  7:59         ` Joel Brobecker
2018-08-31 16:02           ` Sergio Durigan Junior
2018-08-31 11:21         ` Pedro Alves
2018-08-31 16:03           ` Sergio Durigan Junior
2018-09-02 21:21           ` [PATCH] Automatically update "aclocal_m4_deps" when updating gnulib Sergio Durigan Junior
2018-09-03 11:15             ` Pedro Alves
2018-09-03 21:18               ` Sergio Durigan Junior
2018-09-04 11:10                 ` Pedro Alves
2018-09-04 17:58                   ` Sergio Durigan Junior
  -- strict thread matches above, loose matches on Subject: below --
2016-10-12 15:17 [PATCH] Update gnulib to current upstream master Pedro Alves
2016-10-12 16:09 ` Yao Qi
2016-10-12 16:12   ` Pedro Alves
2016-10-12 16:23     ` Pedro Alves
2016-10-12 16:56       ` Eli Zaretskii
2016-10-12 17:10         ` Pedro Alves
2016-10-12 17:31           ` Eli Zaretskii
2016-10-12 16:30     ` Yao Qi

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=87y3cpm90l.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).