From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Add a 'starti' command.
Date: Tue, 19 Sep 2017 18:29:00 -0000 [thread overview]
Message-ID: <5479424e-9777-0754-efe8-0523caef1bdc@redhat.com> (raw)
In-Reply-To: <19338806.QVLJa9ilSl@ralph.baldwin.cx>
On 09/19/2017 06:49 PM, John Baldwin wrote:
> Hmm, how about:
>
> enum run_how
> {
> /* Run program without any explicit stop during startup. */
> RUN_NORMAL,
Sounds fine.
>> You have a "\n" in the middle of some lines above. Was that intended?
>> I'd expect to see instead lines broken at \n, ending with \n\ .
>
> Those were just copy and pasted from the run help. I think they were there
> to avoid overflowing 80 columns in the source. I've rewrapped the text so
> that newlines are at the end.
Thanks.
>> Space before parens, line break after return type.
>> We follow GNU convention in tests too, unless different syntax is
>> relevant for the test.
>
> Ok. (Ironically I copied both the spurious #include and bad style
> from start.c.)
Yeah, sorry about that. It was only in recent years that we
started following that rule; older tests will be using
random styles.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-19 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:08 John Baldwin
2017-09-18 23:15 ` John Baldwin
2017-09-19 14:35 ` Pedro Alves
2017-09-19 18:23 ` John Baldwin
2017-09-19 18:29 ` Pedro Alves [this message]
2017-11-03 13:00 ` Yao Qi
2017-11-15 20:11 ` John Baldwin
2017-11-15 20:23 ` Pedro Alves
2017-11-15 23:32 ` John Baldwin
2017-11-16 10:54 ` Pedro Alves
2017-11-16 12:38 ` [pushed] Fix gdb.base/starti.exp racy test (Re: [PATCH v3] Add a 'starti' command.) Pedro Alves
2017-11-16 18:00 ` John Baldwin
2017-11-16 18:15 ` Pedro Alves
2017-11-16 9:55 ` [PATCH v3] Add a 'starti' command 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=5479424e-9777-0754-efe8-0523caef1bdc@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
/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