From: Phil Muldoon <pmuldoon@redhat.com>
To: "Matt McCormick (thewtex)" <matt@mmmccormick.com>,
Project Archer <archer@sourceware.org>
Subject: Re: [PATCH 2/2] [python] Document gdb.value_history_count
Date: Thu, 17 Dec 2009 09:13:00 -0000 [thread overview]
Message-ID: <4B29F615.7090503@redhat.com> (raw)
In-Reply-To: <4B29F581.1020601@redhat.com>
Apologies, hit reply instead of reply-all. Reply as forwarded.
On 12/17/2009 09:10 AM, Phil Muldoon wrote:
> On 12/15/2009 05:54 AM, Matt McCormick (thewtex) wrote:
>
>> 2009-12-14 Matt McCormick <matt@mmmccormick.com>
>>
>> * gdb/doc/gdb.texinfo: Document gdb.value_history_count.
>
> ChangeLog entries corresponding to documentation patches belong in the
> ChangeLog located in: src/gdb/doc. Also you need to indicate the
> section the documentation patch is altering. So I would write the
> entry as:
>
>> 2009-12-14 Matt McCormick <matt@mmmccormick.com>
>>
>> * gdb.texinfo (Basic Python) : Document gdb.value_history_count.
>
>
> Cheers,
>
> Phil
next prev parent reply other threads:[~2009-12-17 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 21:22 [PATCH 1/2] [python] Add gdb.value_history_count() 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 [this message]
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)
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=4B29F615.7090503@redhat.com \
--to=pmuldoon@redhat.com \
--cc=archer@sourceware.org \
--cc=matt@mmmccormick.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).