Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] doc addition to gdbint.texinfo
Date: Thu, 04 Feb 2010 22:20:00 -0000	[thread overview]
Message-ID: <83zl3ofxsw.fsf@gnu.org> (raw)
In-Reply-To: <20100204213709.C7D4884414@ruffy.mtv.corp.google.com>

> Date: Thu,  4 Feb 2010 13:37:09 -0800 (PST)
> From: dje@google.com (Doug Evans)
> 
> The Testsuite section of gdbint.texinfo is missing docs on at least
> two more DejaGnu variables that are available to be overridden:
> GDB, GDBSERVER.
> 
> Since there's at least three of them (those two plus TRANSCRIPT),
> with more to come, it seemed appropriate to create a new section to
> document them all.

I agree.

> Ok to check in?

Yes, after this:

> +Several variables exist to modify the behavior of the testsuite.
> +
> +@itemize @bullet
> +
> +@item TRANSCRIPT

Please give each variable the @code markup.

> +@smallexample
> +make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver"
> +@end smallexample

Did you try to "make pdf"?  I suspect that this line is too long and
will overflow the right margin.  If it does, please break it into two
(and tell in the text that it is just one long line).

> +The second is to cd to the @file{testsuite} directory and invoke the DejaGnu
> +@kbd{runtest} command directly.

In this context, "runtest" is a name of a command, not a command line
typed at the keyboard.  So @command will be more appropriate than @kbd
here.

OK with these changes.

Thanks.


  reply	other threads:[~2010-02-04 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 21:37 Doug Evans
2010-02-04 22:20 ` Eli Zaretskii [this message]
2010-02-05 18:32   ` Doug Evans

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=83zl3ofxsw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --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