From: Nick Roberts <nick@nick.uklinux.net>
To: Bob Rossi <bob@brasko.net>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] implements MI "-file-list-exec-sections" (updated)
Date: Sat, 01 May 2004 12:08:00 -0000 [thread overview]
Message-ID: <16531.37648.806738.186535@nick.uklinux.net> (raw)
In-Reply-To: <20040501040929.GB17480@white>
> I think everyone agrees, changing the CLI would be the worst possible
> thing GDB could do.
I'm not sure if thats true, I was just talking about timing. Its probably
not reasonable or even realistic to insist that CLI output never changes.
> For some unfortunate reason, every front end would break in some subtle
> way if the output of the CLI was modified. In some way, it doesn't
> really make sense to just coordinate GDB with Emacs and not every other
> front end, right?
Well, GDB and Emacs are both part of the GNU Project. I don't know how much
this counts for, but at the moment GDB issues a new release about twice a year
whereas the last release of Emacs from CVS HEAD was in September 2001. I am
saying that these very different timetables are difficult to work with. As
maintainer of CGDB, you (Bob) are presumably free to make a new release
whenever you wish.
Nick
next prev parent reply other threads:[~2004-05-01 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 21:54 Nick Roberts
2004-05-01 4:09 ` Bob Rossi
2004-05-01 12:08 ` Nick Roberts [this message]
2004-05-02 13:25 ` Bob Rossi
2004-05-07 1:19 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 21:56 Stefan Weyergraf
2004-04-22 22:22 ` Bob Rossi
2004-04-22 23:31 ` Stefan Weyergraf
2004-04-28 21:51 ` Andrew Cagney
2004-05-07 1:20 ` Andrew Cagney
2004-05-06 22:07 ` Stefan Weyergraf
2004-05-12 20:14 ` Andrew Cagney
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=16531.37648.806738.186535@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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