From: Ken Brown <kbrown@cornell.edu>
To: Chong Yidong <cyd@stupidchicken.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Nick Roberts <nickrob@snap.net.nz>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
emacs-devel@gnu.org
Subject: Re: gdb-create-source-file-list and gdb-mi.el
Date: Tue, 29 Nov 2011 10:29:21 -0500 [thread overview]
Message-ID: <4ED4FA51.70901@cornell.edu> (raw)
In-Reply-To: <20180.39867.953048.999489@totara.tehura.co.nz>
On 11/29/2011 3:45 AM, Nick Roberts wrote:
> I think that you're probably more familiar with some of this code than I am
> now. I've don't have much time for emacs development at the moment and I
> don't want to become a bottleneck. So I'm happy for you to commit these
> changes if it's OK with Cyd and Stefan. Ken Brown's patches look good too.
> One, at least, is a regression from gdb-ui.el which probably still has fewer
> issues than gdb-mi.el
Chong and Stefan,
Should I apply my patches, or would you rather they wait for 24.2 at
this point? Here are the references again:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9853
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9858
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9878
Ken
next prev parent reply other threads:[~2011-11-29 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 7:05 Re:gdb-create-source-file-list and gdb-mi.el Nick Roberts
2011-11-25 22:28 ` gdb-create-source-file-list " Ken Brown
2011-11-26 7:00 ` Chong Yidong
2011-11-29 7:52 ` Aneesh Kumar K.V
2011-11-29 8:45 ` Nick Roberts
2011-11-29 15:29 ` Ken Brown [this message]
2011-11-29 18:46 ` gdb-create-source-file-list " Stefan Monnier
2011-11-30 3:32 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 10:29 Aneesh Kumar K.V
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=4ED4FA51.70901@cornell.edu \
--to=kbrown@cornell.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=nickrob@snap.net.nz \
/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.