From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: lekktu@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Removing MULTI_KBOARD
Date: Sat, 02 Aug 2008 12:38:05 +0300 [thread overview]
Message-ID: <uzlnvlptu.fsf@gnu.org> (raw)
In-Reply-To: <200808020927.m729Rnov027876@sallyv1.ics.uci.edu>
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Cc: rms@gnu.org, Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
> Date: Sat, 02 Aug 2008 02:27:49 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > From: Dan Nicolaescu <dann@ics.uci.edu>
> > > Cc: "Juanma Barranquero" <lekktu@gmail.com>, eliz@gnu.org, emacs-devel@gnu.org
> > > Date: Fri, 01 Aug 2008 23:55:57 -0700
> > >
> > > The code was turned off by default, unused and unnecessary, and that has
> > > been explained on the list almost a year ago. If someone has a problem
> > > with that, it would be much more productive to explain why, but not just
> > > hand waving, with some real experience/examples. Otherwise please let
> > > bygones be bygones, it's a terrible waste of time.
> >
> > I did explain why I have a problem with this: it breaks the MSDOS
> > port.
>
> You have handwaved that. Can you please actually explain why you think that?
> I have explained it is not a problem.
How it is not a problem, if the MSDOS port does not support
MULTI_KBOARD? I must have missed the explanation, please repeat it.
> 1. The MSDOS port is broken for other reasons, it has been like that for a
> year. Nobody has complained.
> 2. The MSDOS port was on a widely publicized list of platforms that we
> indented to remove. Nobody requested it to be kept, so RMS approved its
> removal.
> 3. The MSDOS port might never be revived, you have never committed to do
> so, the only statements you have made was "I might do it".
All of these reasons might be invalid tomorrow, if I decide to revive
it tomorrow.
> > . Revert Dan's changes that removed MULTI_KBOARD.
>
> Please do not do such a thing, this would be a very bad case of priority
> inversion: forcing to keep code just because it might (although it is
> doubtful) make it easier to revive a port to a very old, proprietary
> platform with NO ACTIVE USERS, otherwise broken and unmaintained for one
> year, hence a low priority task for a GNU project. The code is an
> inconvenience and requires more work when doing maintenance and
> debugging maintenance on GNU/Linux, i.e a high priority task for GNU.
>
> If the MSDOS port ever gets fixed (which, again, is not sure to happen),
> it can be fixed from a CVS checkout prior to the removal of the
> MULTI_KBOARD code. If it turns out that the MULTI_KBOARD code is
> needed, it can be restored at that time. I stand by my claim that such
> a thing would not be necessary.
>
> > . Replace those #ifdef's that are needed by the MSDOS port (I don't
> > know whether this means all of them or not) with #ifdef MSDOS.
>
> That is even worse, the unnecessary code is still in the way of all
> the GNU/Linux maintainers.
I'm open to other suggestions, but please don't suggest to drop the
MSDOS port until I decide to do that.
next prev parent reply other threads:[~2008-08-02 9:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uzlnvlptu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rms@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.
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.