public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org, eliz@gnu.org
Subject: [PATCH 0/3] deprecate "skip enable/etc.", doc string cleanup
Date: Mon, 18 Apr 2016 15:17:00 -0000	[thread overview]
Message-ID: <047d7b86e1c2f49c8c0530c3db03@google.com> (raw)

Hi.

Trying to finish up a few old sandboxes.

Most commands use "enable foo 1 2 3", but "skip" doesn't.
This patch set does two things:
1) deprecate "skip enable|disable|delete 1 2 3" in favor of
    "enable|disable|delete skip 1 2 3"
2) clean up some doc strings, make them more consistent

For commands that all take a similar set of arguments
one might wish to just the that part of the doc in one
place and then just refer to it. In the interests
of consistency I have not done so as there was a similar
discussion for the explicit locations patch, and it
was decided to just replicate the docs.

1/3: cleanup breakpoint.c doc strings
2/3: deprecate skip enable/etc., clean up skip doc strings
3/3: "display" command doc cleanup

                 reply	other threads:[~2016-04-18 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=047d7b86e1c2f49c8c0530c3db03@google.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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).