From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFA] Submit process record and replay fourth time, 3/8
Date: Wed, 29 Apr 2009 01:43:00 -0000 [thread overview]
Message-ID: <daef60380904281843l55ed4d25pcf482233e4905b19@mail.gmail.com> (raw)
In-Reply-To: <200904282255.35290.pedro@codesourcery.com>
Hi Pedro,
On Wed, Apr 29, 2009 at 05:55, Pedro Alves <pedro@codesourcery.com> wrote:
> On Tuesday 28 April 2009 11:12:03, Hui Zhu wrote:
>
>> 2009-03-21 Hui Zhu <teawater@gmail.com>
>>
>> Process record and replay target.
>>
>> * Makefile.in (record.c): New file.
>> * record.c, record.h: New file.
>>
>> 2008-12-28 Michael Snyder <msnyder@vmware.com>
>> * Comments, spelling, white space clean-ups.
>>
>> 2008-12-26 Michael Snyder <msnyder@vmware.com>
>> * record.h: Don't export record_not_record.
>> * record.c (record_not_record): Rename to in_record_wait.
>> (record_not_record_set): Rename to in_record_wait_set.
>> (record_not_record_cleanup): Rename to in_record_wait_cleanup.
>> (record_store_registers): Check in_record_wait flag.
>> (record_xfer_partial): Ditto.
>>
> ...
>
> Sorry that I have to be the nick-picky-guy again, but, as far as
> I know and can see, we don't use that style of change log
> entry covering the history of the changes that led to the current
> form of the patch. I know I've seen it before in *branches*,
> but never on mainline's ChangeLog file.
>
> The standard form of entry when more than one person did work on a
> patch, is to append the name of the person in the header, like so:
>
> 2009-03-21 Hui Zhu <teawater@gmail.com>
> Michael Snyder <msnyder@vmware.com>
>
> * Makefile.in (SFILES): Add record.c.
> (COMMON_OBS): Add record.o.
> * record.c, record.h: New files.
>
> You'll find plenty examples of entries like that in the
> ChangeLog files.
>
> Would you mind making that change? Thanks in advance.
Of course you are not the nick-picky-guy. You give me a lot of help
to make process record better. :)
Your comment about the changelog is very well. I will change all
changelog like it.
2009-04-29 Hui Zhu <teawater@gmail.com>
Michael Snyder <msnyder@vmware.com>
Process record and replay target.
* Makefile.in (SFILES): Add record.c.
(COMMON_OBS): Add record.o.
* record.c, record.h: New file.
Thanks,
Hui
prev parent reply other threads:[~2009-04-29 1:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 16:02 Hui Zhu
2009-03-25 7:19 ` Hui Zhu
2009-04-15 17:02 ` Hui Zhu
2009-04-22 9:06 ` Hui Zhu
2009-04-27 6:01 ` Hui Zhu
2009-04-27 21:57 ` Pedro Alves
2009-04-28 1:51 ` Hui Zhu
2009-04-28 10:12 ` Hui Zhu
2009-04-28 21:55 ` Pedro Alves
2009-04-29 1:43 ` Hui Zhu [this message]
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=daef60380904281843l55ed4d25pcf482233e4905b19@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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