Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Fix per-thread watchpoint documentation
Date: Tue, 18 Dec 2007 00:43:00 -0000	[thread overview]
Message-ID: <ud4t5jc0i.fsf@gnu.org> (raw)
In-Reply-To: <m3wsrdclri.fsf@codesourcery.com> (message from Jim Blandy on 	Mon, 17 Dec 2007 08:46:09 -0800)

> From: Jim Blandy <jimb@codesourcery.com>
> Date: Mon, 17 Dec 2007 08:46:09 -0800
> 
> 
> The GDB documentation doesn't build at the moment, because the
> per-thread watchpoint documentation introduces an @item outside any
> @table.
> 
> One could fix this by simply wrapping a @table around the new @item,
> but it doesn't seem to me that that description is in the right place
> within its node.
> 
> So, does this look okay?

Yes, but you also changed other places which you didn't announce.  Not
that I object to them, though...

Thanks.


  parent reply	other threads:[~2007-12-17 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 17:13 Jim Blandy
2007-12-17 17:38 ` Luis Machado
2007-12-18  0:43 ` Eli Zaretskii [this message]
2007-12-18 18:27   ` Jim Blandy

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=ud4t5jc0i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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