From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: {PATCH] gdbint.texi
Date: Mon, 15 May 2006 10:19:00 -0000 [thread overview]
Message-ID: <u8xp43qr7.fsf@gnu.org> (raw)
In-Reply-To: <17512.64334.458857.837437@kahikatea.snap.net.nz> (message from Nick Roberts on Tue, 16 May 2006 10:06:06 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 16 May 2006 10:06:06 +1200
> Cc: gdb-patches@sources.redhat.com
>
> > > * 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.)
>
> OK, but I think there can be more slack with documentation, generally.
Yes, but is there a real problem here? How many nodes did you update,
anyway?
prev parent reply other threads:[~2006-05-15 3:34 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 [was Re: RFC: MI output during program execution] 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
2006-05-15 0:56 ` {PATCH] gdbint.texi Nick Roberts
2006-05-15 10:19 ` Eli Zaretskii [this message]
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=u8xp43qr7.fsf@gnu.org \
--to=eliz@gnu.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