Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Update gnulib to current upstream master
Date: Wed, 12 Oct 2016 17:10:00 -0000	[thread overview]
Message-ID: <a6754b20-5e67-dee1-717d-cbc9e9ec1a49@redhat.com> (raw)
In-Reply-To: <83pon5a4ma.fsf@gnu.org>

On 10/12/2016 05:55 PM, Eli Zaretskii wrote:
>> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>> From: Pedro Alves <palves@redhat.com>
>> Date: Wed, 12 Oct 2016 17:23:04 +0100
>>
>> I think now's the perfect time to update, since we're early in
>> the release cycle.
> 
> I agree.  If nothing else, it solves the 2 problems I had with the
> recent MinGW runtime when building GDB 7.12, see
> 
>   https://lists.gnu.org/archive/html/bug-gnulib/2016-10/msg00007.html

For 7.12, might it be a better idea to cherry pick your fix to
the branch though?  The update is not that large, but there's
still a good amount of churn all around.

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-12 17:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 15:17 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 [this message]
2016-10-12 17:31           ` Eli Zaretskii
2016-10-12 16:30     ` Yao Qi
2016-10-18 22:20     ` [pushed] gdb: no longer define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS (Re: [PATCH] Update gnulib to current upstream master) Pedro Alves
2018-08-28 19:59 [PATCH] Update gnulib to current upstream master Sergio Durigan Junior
2018-08-29 16:19 ` Tom Tromey
2018-08-29 16:29   ` Sergio Durigan Junior
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

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=a6754b20-5e67-dee1-717d-cbc9e9ec1a49@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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