From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Update gnulib to current upstream master
Date: Thu, 30 Aug 2018 00:04:00 -0000 [thread overview]
Message-ID: <877ek8wwgr.fsf@tromey.com> (raw)
In-Reply-To: <dba64ca1-4eb4-7b0c-d662-d300102458cc@redhat.com> (Pedro Alves's message of "Wed, 29 Aug 2018 20:06:27 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> It is standard practice when updating gnulib to discuss the set of
Pedro> modules that the exercise brings in due to module dependencies.
Sorry about that, I should have remembered before approving this.
Tom
next prev parent reply other threads:[~2018-08-30 0:04 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
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 [this message]
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=877ek8wwgr.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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