Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] add note on command naming to gdbint.texi
Date: Thu, 03 Jun 2010 19:36:00 -0000	[thread overview]
Message-ID: <m3y6evzz77.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100603181353.E965584396@ruffy.mtv.corp.google.com> (Doug	Evans's message of "Thu, 3 Jun 2010 11:13:53 -0700 (PDT)")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> I'd like to add this to the Coding section of gdbint.texi.

Doug> +GDB U/I commands are written @samp{foo-bar}, not @samp{foo_bar}.

I wonder whether we also have a rule about when to use a hyphen versus
when to use a subcommand.

I don't think that impacts whether this patch should go in.

Tom


  parent reply	other threads:[~2010-06-03 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 18:14 Doug Evans
2010-06-03 18:44 ` Eli Zaretskii
2010-06-03 19:36 ` Tom Tromey [this message]
2010-06-03 20:31   ` Stan Shebs

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=m3y6evzz77.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --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