From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 2/2] Make null_ptid and minus_one_ptid "const"
Date: Mon, 04 Mar 2019 23:30:00 -0000 [thread overview]
Message-ID: <20190304163048.5ef186ef@f29-4.lan> (raw)
In-Reply-To: <20190304202516.19100-3-tromey@adacore.com>
On Mon, 4 Mar 2019 13:25:16 -0700
Tom Tromey <tromey@adacore.com> wrote:
> This makes null_ptid and minus_one_ptid "const". I think this is an
> improvement because it means they can't be accidentally modified.
>
> xgdb/ChangeLog
> 2019-03-04 Tom Tromey <tromey@adacore.com>
>
> * common/ptid.c (null_ptid, minus_one_ptid): Now const.
> * common/ptid.h (null_ptid, minus_one_ptid): Now const.
LGTM.
Kevin
next prev parent reply other threads:[~2019-03-04 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 20:25 [PATCH 0/2] constify null_ptid and minus_one_ptid Tom Tromey
2019-03-04 20:25 ` [PATCH 2/2] Make null_ptid and minus_one_ptid "const" Tom Tromey
2019-03-04 23:30 ` Kevin Buettner [this message]
2019-03-04 20:25 ` [PATCH 1/2] Change iterate_over_lwps to take a gdb::function_view Tom Tromey
2019-03-04 23:28 ` Kevin Buettner
2019-03-12 16:46 ` [PATCH 0/2] constify null_ptid and minus_one_ptid 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=20190304163048.5ef186ef@f29-4.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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