From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: cbiesinger@google.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Update gnulib to current trunk
Date: Thu, 02 Jul 2020 22:02:06 +0300 [thread overview]
Message-ID: <83h7upwxjl.fsf@gnu.org> (raw)
In-Reply-To: <e3c60660-0cb0-dd4d-b710-89404790a8a1@palves.net> (message from Pedro Alves on Thu, 2 Jul 2020 19:49:53 +0100)
> From: Pedro Alves <pedro@palves.net>
> Date: Thu, 2 Jul 2020 19:49:53 +0100
>
> > This fixes two issues on Windows: Update.
> > https://sourceware.org/pipermail/gdb-patches/2020-June/169978.html
>
> This seems to be bringing in a good amount of churn.
Maybe we should just update the two modules which were changed due to
my reports? Would that be safer?
next prev parent reply other threads:[~2020-07-02 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200630184349.4009048-1-cbiesinger@google.com>
2020-06-30 19:19 ` Christian Biesinger
2020-07-02 18:49 ` Pedro Alves
2020-07-02 19:02 ` Eli Zaretskii [this message]
2020-07-02 19:06 ` Pedro Alves
2020-07-06 18:19 ` Christian Biesinger
2020-07-15 2:40 ` Christian Biesinger
2020-07-16 14:56 ` Pedro Alves
2020-08-13 12:24 ` Tom de Vries
2020-08-23 21:37 ` Joel Brobecker
2020-08-23 21:41 ` Joel Brobecker
2020-08-24 13:46 ` Pedro Alves
2020-08-26 22:39 ` Joel Brobecker
2020-08-27 19:41 ` Christian Biesinger
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=83h7upwxjl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).