From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Engelhardt <jengelh@inai.de>,
gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Make "j" an alias of "jump" [was: Re: "j" is now an ambiguous command]
Date: Tue, 18 Sep 2012 20:16:00 -0000 [thread overview]
Message-ID: <m3obl3m6hx.fsf@redhat.com> (raw)
In-Reply-To: <87zk4nun3a.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 18 Sep 2012 13:50:49 -0600")
On Tuesday, September 18 2012, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> 2012-09-18 Sergio Durigan Junior <sergiodj@redhat.com>
> Sergio> * infcmd.c (_initialize_infcmd): Register `j' as an alias for
> Sergio> `jump'.
>
> The code bits are ok.
>
> Thanks for picking this up.
Thanks Tom and Eli.
Checked in:
http://sourceware.org/ml/gdb-cvs/2012-09/msg00100.html
--
Sergio
next prev parent reply other threads:[~2012-09-18 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.01.1209160050010.13178@nerf07.vanv.qr>
2012-09-18 19:44 ` Sergio Durigan Junior
2012-09-18 19:51 ` Tom Tromey
2012-09-18 20:16 ` Sergio Durigan Junior [this message]
2012-09-18 20:07 ` Eli Zaretskii
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=m3obl3m6hx.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jengelh@inai.de \
--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