From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Move gdb/warning.m4 to gdbsupport
Date: Tue, 11 Feb 2020 14:55:00 -0000 [thread overview]
Message-ID: <87eev1dvgt.fsf@tromey.com> (raw)
In-Reply-To: <20200210164024.32445-2-simon.marchi@efficios.com> (Simon Marchi's message of "Mon, 10 Feb 2020 11:40:23 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> This file is used by gdbsupport, gdbserver and gdb, so I think it
Simon> belongs in gdbsupport. Move it there and update the references the
Simon> various acinclude.m4 files.
Makes sense to me.
Simon> gdbsupport/ChangeLog:
Simon> * warning.m4: Move here, from gdb/warning.m4.
Simon> * acinclude.m4: Update warning.m4 path.
Simon> * Makefile.in: Re-generate.
Simon> gdbserver/ChangeLog:
Simon> * acinclude.m4: Update warning.m4 path.
Simon> gdb/ChangeLog:
Simon> * acinclude: Update warning.m4 path.
Simon> * warning.m4: Move to gdbsupport.
Looks good.
Tom
next prev parent reply other threads:[~2020-02-11 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:40 [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Simon Marchi
2020-02-10 16:40 ` [PATCH 3/3] Add -Wstrict-null-sentinel to gdbsupport/warning.m4 Simon Marchi
2020-02-10 16:42 ` Christian Biesinger via gdb-patches
2020-02-10 16:46 ` Simon Marchi
2020-02-11 14:57 ` Tom Tromey
2020-02-11 16:11 ` Simon Marchi
2020-02-10 16:40 ` [PATCH 2/3] Move gdb/warning.m4 to gdbsupport Simon Marchi
2020-02-11 14:55 ` Tom Tromey [this message]
2020-02-11 14:55 ` [PATCH 1/3] gdbsupport: use AM_GDB_WARNINGS Tom Tromey
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=87eev1dvgt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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