From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 4/4] introduce parallel mode
Date: Fri, 02 Aug 2013 19:38:00 -0000 [thread overview]
Message-ID: <83zjszyjbv.fsf@gnu.org> (raw)
In-Reply-To: <87bo5fdho0.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Fri, 02 Aug 2013 13:19:43 -0600
>
> Eli> Looks like it's a matter of taste in this case.
>
> If you really think @itemize is preferred here, I will comply.
I don't think it's preferred. I think both forms are about the same
in this case.
> I'd like to understand your rationale, though.
> If I were writing this from scratch I would not have even considered
> @itemize, but rather @table. I'd like to know when I ought to use
> @itemize in this scenario instead.
@itemize is a way to enumerate things. Which is what this text does.
@table is more suitable to a list of values of a single variable, or a
list of alternatives. Which is also what this text is about.
prev parent reply other threads:[~2013-08-02 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 15:36 [PATCH v2 0/4] introduce test suite "parallel" mode Tom Tromey
2013-08-02 15:36 ` [PATCH v2 1/4] more uses of standard_output_file Tom Tromey
2013-08-02 15:36 ` [PATCH v2 3/4] add caching procs to test suite Tom Tromey
2013-08-02 15:53 ` Pedro Alves
2013-08-02 16:48 ` Tom Tromey
2013-08-02 17:23 ` Pedro Alves
2013-08-02 20:15 ` Tom Tromey
2013-08-02 15:36 ` [PATCH v2 2/4] add standard_temp_file Tom Tromey
2013-08-02 15:36 ` [PATCH v2 4/4] introduce parallel mode Tom Tromey
2013-08-02 18:01 ` Eli Zaretskii
2013-08-02 18:37 ` Tom Tromey
2013-08-02 18:44 ` Eli Zaretskii
2013-08-02 18:48 ` Tom Tromey
2013-08-02 19:17 ` Eli Zaretskii
2013-08-02 19:19 ` Tom Tromey
2013-08-02 19:38 ` Eli Zaretskii [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=83zjszyjbv.fsf@gnu.org \
--to=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