From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] partial fix PR 14777: Add abbrev cmd 'fo' for 'forward-search'.
Date: Fri, 09 Nov 2012 08:35:00 -0000 [thread overview]
Message-ID: <509CC020.3010506@codesourcery.com> (raw)
In-Reply-To: <1352293267-6640-1-git-send-email-yao@codesourcery.com>
On 11/07/2012 09:01 PM, Yao Qi wrote:
> gdb/doc:
> 2012-11-07 Yao Qi<yao@codesourcery.com>
>
> * gdb.texinfo (Search): Add kindex for 'fo'.
> gdb:
> 2012-11-07 Yao Qi<yao@codesourcery.com>
>
> PR gdb/14777.
> * source.c (_initialize_source): Call add_com_alias to abbreviate
> 'forward-search' as 'fo'.
Here is the news entry to this fix, because this fix is visible
to users. OK?
--
Yao
gdb:
2012-11-09 Yao Qi <yao@codesourcery.com>
* NEWS: Mention the fix to the ambiguity of 'fo' command.
---
gdb/NEWS | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 069b84f..5ed029f 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -24,6 +24,9 @@
* The 'cd' command now defaults to using '~' (the home directory) if not
given an argument.
+* The ambiguity of 'fo' command is fixed and it is the abbreviated command
+ of 'forward-search'.
+
* New configure options
--enable-libmcheck/--disable-libmcheck
--
1.7.7.6
next prev parent reply other threads:[~2012-11-09 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 13:01 Yao Qi
2012-11-07 15:13 ` Joel Brobecker
2012-11-07 16:07 ` Pedro Alves
2012-11-08 9:39 ` Yao Qi
2012-11-08 16:11 ` Pedro Alves
2012-11-28 10:10 ` Yao Qi
2012-11-28 10:18 ` Pedro Alves
2012-11-28 10:36 ` Yao Qi
2012-11-28 11:10 ` Pedro Alves
2012-11-28 11:57 ` [committed]: " Yao Qi
2012-11-07 16:10 ` Eli Zaretskii
2012-11-09 8:35 ` Yao Qi [this message]
2012-11-09 8:43 ` 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=509CC020.3010506@codesourcery.com \
--to=yao@codesourcery.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