From: Glenn Morris <rgm@gnu.org>
To: Jean-Philippe Gravel <jpgravel@gmail.com>
Cc: 13845@debbugs.gnu.org
Subject: bug#13845: 24.3.50; gud commands stop responding when using gdb-mi
Date: Tue, 30 Apr 2013 14:54:13 -0400 [thread overview]
Message-ID: <3yobcvetnu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAB3yAohON8JxguoxhmQcQxoUsSo5ohuyD=1xXDX8KCKhdmEwPQ@mail.gmail.com> (Jean-Philippe Gravel's message of "Mon, 29 Apr 2013 23:32:51 -0400")
Jean-Philippe Gravel wrote:
> My branch is available on launchpad:
> https://code.launchpad.net/~jpgravel/emacs/bug13845
>
> Please consider all revisions from 112234 to 112242. Revision 112233
> is already in the trunk.
Could you send the change you propose to install to this address as a
flat diff? I'm assuming it is not enormous.
> - I needed the function cl-find-if and cl-delete-if. It seems there
> is a long history about not using the functions from cl.el at runtime.
It is fine to use cl-lib at runtime, so no problem.
> - I removed two strange ^L characters in gdb-mi.el. Am I right to
> remove them?
No. (And as a general comment don't mix unrelated formatting changes
with commits.)
> Do they mean anything, or are they garbage ASCII
> character that got there by mistake?
They are page separators. See (emacs)Pages.
> - When doing my commit, do I need to specify a bug tracker with the
> --fixes option, or is "--fixes 13845" enough?
Add an entry to ~/.bazaar/bazaar.conf:
[DEFAULT]
bugtracker_debbugs_url = http://debbugs.gnu.org/{id}
then use --fixes debbugs:13845
next prev parent reply other threads:[~2013-04-30 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 2:02 bug#13845: 24.3.50; gud commands stop responding when using gdb-mi Jean-Philippe Gravel
2013-04-30 3:32 ` Jean-Philippe Gravel
2013-04-30 18:54 ` Glenn Morris [this message]
2013-05-01 2:46 ` Jean-Philippe Gravel
2013-05-02 2:20 ` Glenn Morris
2013-05-05 5:28 ` Stefan Monnier
2013-05-06 2:05 ` Jean-Philippe Gravel
2013-05-14 18:52 ` Jean-Philippe Gravel
2013-05-14 19:23 ` Glenn Morris
2013-05-15 1:47 ` Jean-Philippe Gravel
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=3yobcvetnu.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=13845@debbugs.gnu.org \
--cc=jpgravel@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.