From: "Eli Zaretskii" <eliz@gnu.org>
To: Nick Roberts <nickrob@gnu.org>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [Commit] New file
Date: Tue, 01 Jun 2004 22:21:00 -0000 [thread overview]
Message-ID: <7137-Tue01Jun2004232600+0300-eliz@gnu.org> (raw)
In-Reply-To: <16572.57896.656817.426622@nick.uklinux.net> (message from Nick Roberts on Tue, 1 Jun 2004 21:08:08 +0100)
> From: Nick Roberts <nickrob@gnu.org>
> Date: Tue, 1 Jun 2004 21:08:08 +0100
>
> I think Andrew is (wisely) declining to pick up the gauntlet that you threw
> down in an earlier e-mail. You've certainly made your opinion clear but you
> don't seem to be offering an alternative.
I did offer an alternative: disregard my opinion and do what you think
is right anyway. That wasn't hollow rhetoric: I really meant what I
said.
> You talk of bit-rot but this could
> equally apply to GDB/MI if front-ends don't adopt this interface.
Let me repeat: my assessment is that the Emacs interface will bitrot
much faster than the MI one.
> I see new MI commands that Emacs needs and I would like to discuss their
> implementation within the context of gdb-mi.el. Up till now the entry level to
> try out gdb-mi.el was to check out CVS versions of both GDB and Emacs and
> download the file from my homepage. Rather unsurprisingly, I've had no
> feedback. After the next release of GDB and Emacs, typing M-x gdbmi would be
> enough. Its about lowering the entry threshold.
If we are waiting for both Emacs and GDB to be released, then it
doesn't matter in which one of them users will find gdb-mi.el, right?
So why not put it in Emacs?
> I do this work for fun and because I think it has social value. It ceases to
> be fun if there are disagreements. If GDB maintainers want to remove this file
> then I certainly won't contest it. I will, however, look for a more profitable
> way to spend my time.
I'm sorry that you feel that way, but how can I help it? I do have a
dissenting opinion which is based on past experience, and I thought I
expressed my opinion with all due respect and in a polite and
civilized manner; if the mere fact that there are disagreements is
taken as a reason to stop your contributions, what alternative do _I_
have except shut up? How else can I voice my opinions without causing
people to take offense and leave?
next prev parent reply other threads:[~2004-06-01 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 20:07 Nick Roberts
2004-05-25 22:36 ` Andrew Cagney
2004-05-26 9:54 ` Eli Zaretskii
2004-05-26 9:51 ` Eli Zaretskii
2004-05-26 16:45 ` Andrew Cagney
2004-05-27 7:23 ` Eli Zaretskii
2004-05-27 20:19 ` Andrew Cagney
2004-05-28 7:54 ` Eli Zaretskii
2004-05-28 19:52 ` Nick Roberts
2004-05-31 19:07 ` Andrew Cagney
2004-06-01 4:35 ` Eli Zaretskii
2004-06-01 20:09 ` Nick Roberts
2004-06-01 22:21 ` Eli Zaretskii [this message]
2004-05-26 20:43 ` Nick Roberts
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=7137-Tue01Jun2004232600+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@gnu.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