From: "Matthew McCormick (thewtex)" <matt@mmmccormick.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [PATCH] [python] Add gdb.value_history_count()
Date: Wed, 06 Jan 2010 05:10:00 -0000 [thread overview]
Message-ID: <f23d1cbc1001052110t3281a66k45064140ffc500db@mail.gmail.com> (raw)
In-Reply-To: <4B4351CD.5060804@redhat.com>
Thanks for your suggestions.
On Tue, Jan 5, 2010 at 8:50 AM, Phil Muldoon <pmuldoon@redhat.com> wrote:
> On 12/30/2009 05:16 PM, Matt McCormick wrote:
>
> Looks good. As this is Tom's branch he will have to note whether it
> can be checked in or not. Some small nits:
>
>
>
>> gdb/doc/ChangeLog
>>
>> 2009-30-12 Matt McCormick <matt@mmmccormick.com>
>>
>> * doc/gdb.texinfo (Basic Python): Document gdb.value_history_count.
>
>
> As there is a ChangeLog in the doc/ directory, the paths should be
> relative to the ChangeLog. So in this case, the doc/ prefix is not
> necessary.
>
Logical.
>
>> gdb/testsuite/ChangeLog
>>
>> 2009-30-12 Matt McCormick <matt@mmmccormick.com>
>>
>> * testsuite/gdb.python/py-value.exp (test_value_history_count): Test
>> gdb.value_history_count.
>
>
> Same here with testsuite/.
>
>> +@findex gdb.value_history_count
>> +@defun value_history_count
>> +Return an int corresponding to the number of entries in the value history
>> +(@pxref{Value History}).
>> +@end defun
>
>
> Missing period at the end of that sentence.
>
>>
>> +/* This returns the number of entries in the value history. */
>> +
>> +int get_value_history_count();
>> +
>
> Need a space before the '('.
>
> And git diff --check reports a rogue whitespace ;)
>
> git diff --check
> gdb/testsuite/gdb.python/py-value.exp:277: trailing whitespace.
>
Git + extra whitespace = bull + red flag.
> Cheers!
>
> Phil
>
Thanks, Phil. Will post an update.
next prev parent reply other threads:[~2010-01-06 5:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 21:22 [PATCH 1/2] " Matt McCormick (thewtex)
2009-12-13 21:22 ` [PATCH 2/2] [python] Document gdb.value_history_count() Matt McCormick (thewtex)
2009-12-15 5:51 ` Matthew McCormick (thewtex)
2009-12-15 5:55 ` [PATCH 1/2] [python] Add gdb.value_history_count() Matt McCormick (thewtex)
2009-12-15 5:55 ` [PATCH 2/2] [python] Document gdb.value_history_count Matt McCormick (thewtex)
[not found] ` <4B29F581.1020601@redhat.com>
2009-12-17 9:13 ` Phil Muldoon
2009-12-17 8:59 ` [PATCH 1/2] [python] Add gdb.value_history_count() Phil Muldoon
2009-12-17 14:34 ` Matthew McCormick (thewtex)
2009-12-30 17:06 ` Matthew McCormick (thewtex)
2009-12-30 17:09 ` [PATCH] " Matt McCormick
2009-12-30 17:17 ` Matt McCormick
2010-01-05 14:51 ` Phil Muldoon
2010-01-05 19:49 ` Tom Tromey
2010-01-06 5:10 ` Matthew McCormick (thewtex) [this message]
2010-01-06 5:11 ` Matt McCormick
2010-01-17 19:40 ` Matt McCormick
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=f23d1cbc1001052110t3281a66k45064140ffc500db@mail.gmail.com \
--to=matt@mmmccormick.com \
--cc=archer@sourceware.org \
--cc=pmuldoon@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).