Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add CTF support to GDB [4/4] doc
Date: Fri, 23 Nov 2012 07:40:00 -0000	[thread overview]
Message-ID: <83sj80u5rs.fsf@gnu.org> (raw)
In-Reply-To: <50AEDF18.6090707@mentor.com>

> Date: Fri, 23 Nov 2012 10:27:36 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: <gdb-patches@sourceware.org>
> 
> Following part is for NEWS:
> * GDB now has the ability to read and write trace buffer in common trace
>    format (CTF).  To create a CTF trace file, use "tsave -ctf <filename>",
>    and to use it, do "target ctf <name>".
                    ^^
"use"

> +By default, this command will save trace frame into tfile format.
> +You can supply the optional argument @code{-ctf} to save date in CTF
> +format.  The Common Trace Format (CTF) is proposed as a trace format

Use @dfn when you first introduce new terminology:

  The @dfn{Common Trace Format} (CTF) is proposed as a trace format ...

> +that suits the needs of the embedded, telecom, high-performance
> +and kernel communities.  Please goto @url{http://www.efficios.com/ctf}
> +get more information about it.       ^^^^

You want @indicateurl, not @url here.

OK with these changes.


  reply	other threads:[~2012-11-23  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  1:46 Hui Zhu
2012-11-21 17:37 ` Eli Zaretskii
2012-11-23  2:28   ` Hui Zhu
2012-11-23  7:40     ` Eli Zaretskii [this message]
2012-11-27 11:17       ` Hui Zhu
2012-11-27 18:11         ` Eli Zaretskii
2012-11-28  1:40           ` Hui Zhu
2012-11-28  2:44             ` Yao Qi
2012-11-28  4:56               ` Hui Zhu
     [not found]                 ` <50B5A064.2010007@codesourcery.com>
2012-11-28  5:52                   ` Hui Zhu
2012-11-28 17:40                     ` Eli Zaretskii
2013-01-14 12:26                       ` Hui Zhu
2013-01-14 16:05                         ` 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=83sj80u5rs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.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