Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: {PATCH] gdbint.texi [was Re: RFC: MI output during program execution]
Date: Sun, 14 May 2006 19:45:00 -0000	[thread overview]
Message-ID: <uody04ckz.fsf@gnu.org> (raw)
In-Reply-To: <17510.53117.846489.479963@farnswood.snap.net.nz> (message from 	Nick Roberts on Sun, 14 May 2006 18:34:37 +1200)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 14 May 2006 18:34:37 +1200
> Cc: gdb-patches@sources.redhat.com
> 
> gdbint.texinfo uses gdb as a module name in the node "Versions and Branches"
> but still refers to dejagnu elsewhere so I've tried to remove all those which
> are inappropriate.  Andrew specifically refers to releases 5.0, 5.1 and 5.2 but
> I've not tried to generalise this or update to more recent numbers but Joel
> might like to do this as he goes through the process for GDB 6.5.
> 
> I've also changed a bit of punctuation and spelling.

Thanks.  This is okay, but please fix the following minor problems:

> 	* gdbint.texinfo: Remove details for including DejaGnu.

This needs to state every node in which you made a change.  (Nodes are
the Texinfo equivalents of C functions, as far as ChangeLog entries
are concerned.)

> ! in gdb, e.g. as corefiles, as forked processes, and as some opaque

There should be a @: after "e.g.", to signal TeX that the second
period does not end a sentence.

> ! By using @kbd{-D YYYY-MM-DD-gmt} the branch is forced to an exact
                                    ^
A comma is missing here.

> ! Insight which includes GDB is tagged at the same time.

Please use @value{GDBN} instead a literal GDB.  Also, please add a
comma after "Insight".

> ! gdb/ gdb-5.2.tar insight/ insight-5.2.tar

Please replace 5.2 with something more recent, or perhaps even some
future version (10.1, why not?).


  reply	other threads:[~2006-05-14 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17458.60694.135878.624750@farnswood.snap.net.nz>
     [not found] ` <20060404220637.GA12064@nevyn.them.org>
     [not found]   ` <17486.36188.127822.347550@farnswood.snap.net.nz>
     [not found]     ` <20060504150414.GE32605@nevyn.them.org>
     [not found]       ` <17508.18716.564160.93092@farnswood.snap.net.nz>
     [not found]         ` <20060512124331.GA3460@nevyn.them.org>
2006-05-13  2:28           ` New branch " Nick Roberts
2006-05-13  8:03             ` Daniel Jacobowitz
2006-05-15 16:58               ` PAUL GILLIAM
2006-05-13  9:07             ` Eli Zaretskii
2006-05-13  9:21               ` Nick Roberts
2006-05-13 10:34                 ` Eli Zaretskii
2006-05-13 10:59                   ` Nick Roberts
2006-05-14  7:35       ` {PATCH] gdbint.texi " Nick Roberts
2006-05-14 19:45         ` Eli Zaretskii [this message]
2006-05-15  0:56           ` {PATCH] gdbint.texi Nick Roberts
2006-05-15 10:19             ` 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=uody04ckz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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