Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [PATCH] add @kindex for catchpoints
Date: Tue, 03 Dec 2013 20:39:00 -0000	[thread overview]
Message-ID: <83bo0x4ql1.fsf@gnu.org> (raw)
In-Reply-To: <1386101307-17383-1-git-send-email-tromey@redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: Tom Tromey <tromey@redhat.com>
> Date: Tue,  3 Dec 2013 13:08:27 -0700
> 
> I wanted to find the docs for "catch load" the other day, and I found
> out that this isn't in the index.  It seems to me that each command
> ought to be in the index for quick reference like this, so this patch
> adds an @kindex (chosen because it seems to be what the rest of the
> manual does) for each "catch" subcommand.

Thanks.  Yes, each command should have an index entry.

Please commit this.


      reply	other threads:[~2013-12-03 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 20:08 Tom Tromey
2013-12-03 20:39 ` 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=83bo0x4ql1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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