From: Tom Tromey <tom@tromey.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Pedro Alves <palves@redhat.com>, Tom Tromey <tom@tromey.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [RFC 2/2] Move gdb's xmalloc and friends to new file
Date: Sat, 13 Jul 2019 16:04:00 -0000 [thread overview]
Message-ID: <87d0idzzsl.fsf@tromey.com> (raw)
In-Reply-To: <5B7E81C9-C5FC-47AA-AFE9-61031E9C276A@arm.com> (Alan Hayward's message of "Wed, 3 Jul 2019 16:18:28 +0000")
>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:
Alan> Any objection upping the minimum make version to 3.82 ?
Alan> If so I can raise a patch to add a statement to the NEWS file (similar to
Alan> the one that already exists).
That would be fine by me.
Tom
next prev parent reply other threads:[~2019-07-13 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:30 [RFC 0/2] Let's discuss moving gdbserver to top-level Tom Tromey
2019-05-30 21:30 ` [RFC 1/2] Remove linux-waitpid.c debugging code Tom Tromey
2019-06-03 14:57 ` Simon Marchi
2019-06-03 16:32 ` Tom Tromey
2019-06-05 9:32 ` Pedro Alves
2019-05-30 21:30 ` [RFC 2/2] Move gdb's xmalloc and friends to new file Tom Tromey
2019-06-03 15:03 ` Simon Marchi
2019-06-03 16:33 ` Tom Tromey
2019-06-05 9:40 ` Pedro Alves
2019-06-05 22:33 ` Tom Tromey
2019-06-17 15:45 ` Alan Hayward
2019-06-17 17:43 ` Tom Tromey
2019-06-17 18:37 ` Pedro Alves
2019-06-18 9:31 ` Alan Hayward
2019-07-03 16:18 ` Alan Hayward
2019-07-13 16:04 ` Tom Tromey [this message]
2019-07-16 19:47 ` Pedro Alves
2019-06-03 10:24 ` [RFC 0/2] Let's discuss moving gdbserver to top-level Alan Hayward
2019-06-03 13:13 ` Tom Tromey
2019-06-03 14:27 ` Simon Marchi
2019-06-03 16:30 ` Tom Tromey
2019-06-05 9:16 ` Pedro Alves
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=87d0idzzsl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).