From: Tom Tromey <tom@tromey.com>
To: "Andrew Burgess \(Code Review\)" <gerrit@gnutoolchain-gerrit.osci.io>
Cc: Tom Tromey <tromey@sourceware.org>,
gdb-patches@sourceware.org, gnutoolchain-gerrit@osci.io
Subject: Re: [review] Use cmd_list_element::doc_allocated for Python commands
Date: Sun, 17 Nov 2019 01:06:00 -0000 [thread overview]
Message-ID: <87r227nwg6.fsf@tromey.com> (raw)
In-Reply-To: <20191116092136.27F9B20AF6@gnutoolchain-gerrit.osci.io> (Andrew Burgess's message of "Sat, 16 Nov 2019 04:21:34 -0500")
>>>>> "Andrew" == Andrew Burgess (Code Review) <gerrit@gnutoolchain-gerrit.osci.io> writes:
Andrew> Does this comment need updating now?
Yeah, though it's updated again in a subsequent patch.
Tom
next prev parent reply other threads:[~2019-11-17 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:03 Tom Tromey (Code Review)
2019-11-16 9:21 ` Andrew Burgess (Code Review)
2019-11-17 1:06 ` Tom Tromey [this message]
2019-11-17 21:52 ` [review v2] " Tom Tromey (Code Review)
2019-11-26 21:29 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-26 21:29 ` Sourceware to Gerrit sync (Code Review)
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=87r227nwg6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=gerrit@gnutoolchain-gerrit.osci.io \
--cc=gnutoolchain-gerrit@osci.io \
--cc=tromey@sourceware.org \
/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).