From: "Richard M. Stallman" <rms@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: eliz@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Removing MULTI_KBOARD
Date: Sun, 24 Aug 2008 01:34:54 -0400 [thread overview]
Message-ID: <E1KX8Fa-0007AY-AE@fencepost.gnu.org> (raw)
In-Reply-To: <200808231913.m7NJDQxZ002663@sallyv1.ics.uci.edu> (message from Dan Nicolaescu on Sat, 23 Aug 2008 12:13:24 -0700)
So you are in effect saying that you preemptive attack was baseless and
without any technical justification (the HR approach was so wrong that's
not even worth disscussing). Refusing to provide a technical
justification after so many requests is quite telling. Thank you.
It was entirely reasonable for Eli object to a change that looked like
it would make things more difficult for him -- he did not have to try
to actually do the work before he could object to this.
The fact that he ultimately went along with the change, rather than
undoing it, argues that removing the no-MULTI_KBOARD code was a good
change. But it doesn't change the conclusion that you should have
asked.
next prev parent reply other threads:[~2008-08-24 5:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1KOODr-0006yO-BJ@monty-python.gnu.org>
2008-07-31 3:19 ` Removing MULTI_KBOARD Eli Zaretskii
2008-07-31 3:43 ` Dan Nicolaescu
2008-07-31 18:09 ` Eli Zaretskii
2008-07-31 19:21 ` Dan Nicolaescu
2008-08-01 7:03 ` Eli Zaretskii
2008-08-01 12:09 ` Dan Nicolaescu
2008-08-01 12:20 ` Juanma Barranquero
2008-08-02 5:12 ` Richard M Stallman
2008-08-02 6:55 ` Dan Nicolaescu
2008-08-02 7:45 ` Eli Zaretskii
2008-08-02 9:27 ` Dan Nicolaescu
2008-08-02 9:38 ` Eli Zaretskii
2008-08-02 10:10 ` Jason Rumney
2008-08-02 14:07 ` Chong Yidong
2008-08-02 17:29 ` Eli Zaretskii
2008-08-02 22:49 ` Nick Roberts
2008-08-02 23:58 ` Lennart Borgman (gmail)
2008-08-03 3:24 ` Eli Zaretskii
2008-08-03 18:20 ` Stefan Monnier
2008-08-04 1:15 ` Dan Nicolaescu
2008-08-04 19:10 ` Stefan Monnier
2008-08-05 3:25 ` Eli Zaretskii
2008-08-07 19:37 ` Stefan Monnier
2008-08-12 18:08 ` Eli Zaretskii
2008-08-23 18:05 ` Eli Zaretskii
2008-08-23 18:24 ` Dan Nicolaescu
2008-08-23 19:03 ` Eli Zaretskii
2008-08-23 19:13 ` Dan Nicolaescu
2008-08-23 20:15 ` Eli Zaretskii
2008-08-23 21:01 ` Dan Nicolaescu
2008-08-24 5:34 ` Richard M. Stallman [this message]
2008-08-24 9:36 ` Dan Nicolaescu
2008-08-24 10:15 ` Juanma Barranquero
2008-08-24 18:21 ` Eli Zaretskii
2008-08-26 21:32 ` Stefan Monnier
2008-08-23 20:18 ` Chong Yidong
2008-08-23 20:53 ` Eli Zaretskii
2008-08-26 21:35 ` Stefan Monnier
2008-08-03 5:53 ` Miles Bader
2008-08-03 1:32 ` Richard M. Stallman
2008-08-03 1:33 ` Richard M. Stallman
2008-08-01 13:30 ` Eli Zaretskii
2008-08-01 13:41 ` Dan Nicolaescu
2008-08-01 13:54 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1KX8Fa-0007AY-AE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).