From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Re-generate gnulib import
Date: Mon, 30 Jul 2018 21:11:00 -0000 [thread overview]
Message-ID: <87lg9so2d7.fsf@tromey.com> (raw)
In-Reply-To: <1532969774-20190-1-git-send-email-simon.marchi@ericsson.com> (Simon Marchi's message of "Mon, 30 Jul 2018 12:56:14 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> I noticed that re-generating our gnulib import introduced some changes.
Simon> I supposed that this comes from the recent upgrade to autoconf 2.69
Simon> (though I haven't checked).
Simon> Tested by rebuilding on GNU/Linux x86-64 and mingw (cross-compiled from
Simon> GNU/Linux).
It seems like a good idea to put this in.
Tom
next prev parent reply other threads:[~2018-07-30 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 16:56 Simon Marchi
2018-07-30 21:11 ` Tom Tromey [this message]
2018-07-31 14:10 ` [PP?] " Simon Marchi
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=87lg9so2d7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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