From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>,
tromey@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [MI tracepoints 9/9] documentation
Date: Fri, 26 Mar 2010 08:08:00 -0000 [thread overview]
Message-ID: <201003261108.45867.vladimir@codesourcery.com> (raw)
In-Reply-To: <83d3ysgprv.fsf@gnu.org>
[-- Attachment #1: Type: Text/Plain, Size: 564 bytes --]
On Thursday 25 March 2010 22:33:24 Eli Zaretskii wrote:
> > Date: Thu, 25 Mar 2010 11:12:09 -0700
> > From: Stan Shebs <stan@codesourcery.com>
> > CC: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com,
> > gdb-patches@sources.redhat.com
> >
> > > Is comma actually required per english gramamar, or this is
> > > texinfo quirk?
> > >
> > It's a little of both actually. :-)
>
> Right. But mostly, it's a Texinfo quirk.
Thanks for clarifying. I've checked in the below.
Thanks,
--
Vladimir Prus
CodeSourcery
vladimir@codesourcery.com
(650) 331-3385 x722
[-- Attachment #2: comma.diff --]
[-- Type: text/x-patch, Size: 1228 bytes --]
? .kdev4
Index: gdb/doc/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
retrieving revision 1.1026
diff -u -p -r1.1026 ChangeLog
--- gdb/doc/ChangeLog 26 Mar 2010 01:46:28 -0000 1.1026
+++ gdb/doc/ChangeLog 26 Mar 2010 08:05:16 -0000
@@ -1,3 +1,7 @@
+2010-03-26 Vladimir Prus <vladimir@codesourcery.com>
+
+ * gdb.texinfo (GDB/MI Tracepoint Commands): Add comma after @xref.
+
2010-03-24 Stan Shebs <stan@codesourcery.com>
* gdb.texinfo (Tracepoint Packets): Document trace error status.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.684
diff -u -p -r1.684 gdb.texinfo
--- gdb/doc/gdb.texinfo 26 Mar 2010 01:46:28 -0000 1.684
+++ gdb/doc/gdb.texinfo 26 Mar 2010 08:05:18 -0000
@@ -26050,7 +26050,7 @@ the @samp{found} field has value of @sam
@item frame
The information about the frame corresponding to the found trace
frame. This field is present only if a trace frame was found.
-@xref{GDB/MI Frame Information} for description of this field.
+@xref{GDB/MI Frame Information}, for description of this field.
@end table
next prev parent reply other threads:[~2010-03-26 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 9:04 Vladimir Prus
2010-03-14 18:25 ` Eli Zaretskii
2010-03-16 13:56 ` Vladimir Prus
2010-03-24 21:32 ` Tom Tromey
2010-03-24 21:41 ` Vladimir Prus
2010-03-24 21:43 ` Tom Tromey
2010-03-25 4:06 ` Eli Zaretskii
2010-03-25 17:30 ` Vladimir Prus
2010-03-25 17:36 ` Vladimir Prus
2010-03-25 18:12 ` Stan Shebs
2010-03-25 19:33 ` Eli Zaretskii
2010-03-26 8:08 ` Vladimir Prus [this message]
2010-03-26 8:50 ` 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=201003261108.45867.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=stan@codesourcery.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).