From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fix build with GNU Make 3.81
Date: Thu, 19 Dec 2019 17:29:00 -0000 [thread overview]
Message-ID: <87h81wcjgl.fsf@tromey.com> (raw)
In-Reply-To: <ecd4e216-c528-cf05-6a5a-e41ae0c0d79a@simark.ca> (Simon Marchi's message of "Sat, 14 Dec 2019 13:21:02 -0500")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> I don't mind if we merge simple fixes like that, as long as it doesn't compromise
Simon> building with newer versions. Like, if there was a super-duper cool feature of
Simon> make 3.82 that would really simplify our lives, we would still prefer using that
Simon> over keeping compatibility with make 3.81.
Sounds reasonable to me.
Simon> I'll let Tom decide, since he introduced that new file.
The patch looks ok to me. Thanks.
Tom
next prev parent reply other threads:[~2019-12-19 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 8:15 Bernd Edlinger
2019-12-14 18:21 ` Simon Marchi
2019-12-19 17:29 ` Tom Tromey [this message]
2019-12-23 7:30 ` Joel Brobecker
2020-07-15 8:19 ` Tom de Vries
2020-07-15 13:44 ` Simon Marchi
2020-07-15 18:30 ` Tom de Vries
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=87h81wcjgl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).