Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] Add support for user-defined prefixed commands
Date: Wed, 14 Jan 2009 20:32:00 -0000	[thread overview]
Message-ID: <20090114203135.GA15499@caradoc.them.org> (raw)
In-Reply-To: <20081201210608.GA20385@caradoc.them.org>

On Mon, Dec 01, 2008 at 04:06:08PM -0500, Daniel Jacobowitz wrote:
> This patch allows "define" to take more than one word for the name of
> the command.  It does not allow the creation of new prefix commands,
> but you can add commands to a prefix.  For instance, "define target
> foo" to implement the "target foo" command, which sits next to
> "target sim" and "target remote" and works just like them.

I've belatedly committed this.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2009-01-14 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 21:06 Daniel Jacobowitz
2008-12-01 21:14 ` Eli Zaretskii
2009-01-14 20:32 ` Daniel Jacobowitz [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=20090114203135.GA15499@caradoc.them.org \
    --to=drow@false.org \
    --cc=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