From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH]testsuite: test for disconnected-tracing
Date: Thu, 05 Apr 2012 11:51:00 -0000 [thread overview]
Message-ID: <4F7D8715.9040509@redhat.com> (raw)
In-Reply-To: <4F7D5456.9080806@mentor.com>
On 04/05/2012 09:14 AM, Hui Zhu wrote:
> I post a new version patch according to your comments.
> And I have test it with gdb-7.4 and got fail.
Thanks. Only a few nits remain, and this is technically ready to
check in. See below.
However, what's the status of your copyright assignment? Last I
heard (and from what I see in FSF's copyright assignment records), we
still can't accept changes from you on behalf of Mentor. :-(
> 2012-04-05 Hui Zhu <hui_zhu@mentor.com>
>
> * gdb.trace/Makefile.in (PROGS): Add
> disconnected-tracing.
This fits fine on a single line. Please do that.
> * gdb.trace/disconnected-tracing.c: New file.
> * gdb.trace/disconnected-tracing.exp: New file.
>
> --- /dev/null
> +++ b/testsuite/gdb.trace/disconnected-tracing.c
...
> +
> +int
> +main()
Might as well follow the coding standards, and add a space before parens.
> +{
> + return 0;
> +}
> \ No newline at end of file
^^^^^^^^^^^^^^^^^^^^^^^^^
Please add a newline.
--
Pedro Alves
next prev parent reply other threads:[~2012-04-05 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 14:00 Hui Zhu
2012-03-28 18:51 ` Tom Tromey
2012-03-29 1:17 ` Hui Zhu
2012-03-29 11:37 ` Pedro Alves
2012-04-05 8:14 ` Hui Zhu
2012-04-05 11:51 ` Pedro Alves [this message]
2012-04-11 5:58 ` Hui Zhu
2012-05-10 4:19 ` Hui Zhu
2012-05-10 11:57 ` Pedro Alves
2012-05-10 15:05 ` Hui Zhu
2012-05-10 15:10 ` Pedro Alves
2012-05-11 0:59 ` Hui Zhu
2012-05-11 10:45 ` Pedro Alves
2012-05-14 2:25 ` Hui Zhu
2012-04-08 7:59 ` Yao Qi
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=4F7D8715.9040509@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--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