Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 4/4] introduce parallel mode
Date: Fri, 02 Aug 2013 18:37:00 -0000	[thread overview]
Message-ID: <87mwp0c52c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <834nb8yntk.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Aug	2013 21:01:11 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> From: Tom Tromey <tromey@redhat.com>
>> Cc: Tom Tromey <tromey@redhat.com>
>> Date: Fri,  2 Aug 2013 09:36:13 -0600
>> 
>> * gdbint.texinfo (Testsuite): Use @table, not @itemize.

Eli> I wonder why.

The list is really a 2-column table -- each @item introduces a runtest
variable and then defines its purpose.  This is what @table is for.
If you look at the current code, it uses @item @code{...}
for each one, which I think is a clue that it is incorrect.

Tom


  reply	other threads:[~2013-08-02 18:37 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 [this message]
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

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=87mwp0c52c.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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