From: Kevin Pouget <kevin.pouget@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC - Python] New ObjFile event
Date: Fri, 07 Oct 2011 07:54:00 -0000 [thread overview]
Message-ID: <CAPftXULTd5CR_Cfz_JcjDBySK3c8O7-oiAM8d-7EiSnHngDKEw@mail.gmail.com> (raw)
In-Reply-To: <CAPftXUJJorkLWmNF7vQEFHs+XCQUrQKSS3ssLnpWC=S5C43Vcw@mail.gmail.com>
On Fri, Oct 7, 2011 at 9:40 AM, Kevin Pouget <kevin.pouget@gmail.com> wrote:
> On Wed, Oct 5, 2011 at 7:40 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Kevin Pouget <kevin.pouget@gmail.com>
>>> Date: Wed, 5 Oct 2011 13:10:18 +0200
>>> Cc: gdb-patches@sourceware.org
>>>
>>> + ** A new event "gdb.newobjfile" has been added.
>>> +
>>
>> Maybe say also something like "triggered by loading a new object file."
>>
>>> +@item events.new_objfile
>>> +Emits @code{gdb.NewObjFileEvent} which indicates that a new object-file has
>>
>> "object file", without the hyphen.
>>
>>> +been loaded by @value{GDBN}. @code{gdb.NewObjFileEvent} has one attribute:
>> ^^
>> Two spaces, please.
>>
>> Okay with those changes.
>>
>> Thanks.
>>
>
> commited with the modifications you asked for:
> http://sourceware.org/ml/gdb-cvs/2011-10/msg00034.html
>
> thanks,
>
> Kevin
>
I've also commited
http://sourceware.org/ml/gdb-cvs/2011-10/msg00035.html to fix the
mistake I did with ChangeLogs, everything was is gdb/ChangeLog instead
of testsuite/ChangeLog and doc/ChangeLog, sorry for that
next prev parent reply other threads:[~2011-10-07 7:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimybJtpUzy13FuLxQQMJfeWQuf3-cgqGmu23Bq5@mail.gmail.com>
2011-03-28 8:49 ` Kevin Pouget
2011-03-28 8:51 ` Kevin Pouget
2011-03-28 9:00 ` Phil Muldoon
2011-03-28 8:54 ` Phil Muldoon
2011-03-28 9:03 ` Phil Muldoon
2011-03-28 10:02 ` Kevin Pouget
2011-03-28 20:28 ` Tom Tromey
2011-03-29 11:11 ` Kevin Pouget
2011-03-30 11:32 ` Kevin Pouget
2011-03-30 12:14 ` Phil Muldoon
2011-03-30 12:15 ` Kevin Pouget
2011-05-19 20:21 ` Tom Tromey
2011-05-23 8:44 ` Kevin Pouget
2011-09-01 9:56 ` Kevin Pouget
2011-09-01 11:01 ` Eli Zaretskii
2011-09-01 11:09 ` Kevin Pouget
2011-10-03 16:32 ` Tom Tromey
[not found] ` <CAPftXULEe9R4m7tF=vtJe6NTXHSFAkXgsHCPb3r0mU4wKx0FFg@mail.gmail.com>
2011-10-04 8:25 ` Kevin Pouget
2011-10-04 17:02 ` Tom Tromey
2011-10-05 11:10 ` Kevin Pouget
2011-10-05 14:16 ` Tom Tromey
2011-10-05 17:40 ` Eli Zaretskii
2011-10-07 7:40 ` Kevin Pouget
2011-10-07 7:54 ` Kevin Pouget [this message]
2011-10-07 8:37 Andreas Tobler
2011-10-07 8:44 ` Kevin Pouget
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=CAPftXULTd5CR_Cfz_JcjDBySK3c8O7-oiAM8d-7EiSnHngDKEw@mail.gmail.com \
--to=kevin.pouget@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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