From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, stefankangas@gmail.com,
drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Platform independent graphical display for Emacs
Date: Sat, 25 Dec 2021 14:59:34 +0200 [thread overview]
Message-ID: <6db252bf-7f0a-5c9e-544e-f2fccb488f82@yandex.ru> (raw)
In-Reply-To: <83ilvcris5.fsf@gnu.org>
On 25.12.2021 15:06, Eli Zaretskii wrote:
>> Cc: stefankangas@gmail.com, luangruo@yahoo.com, drew.adams@oracle.com,
>> emacs-devel@gnu.org
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Sat, 25 Dec 2021 13:57:40 +0200
>>
>>> So you'd suggest to the OP to develop the software in the hope that
>>> all of the above will happen? And if it doesn't, just agree for the
>>> results to be abandoned? The OP would have to agree to that.
>>
>> I suppose.
>>
>> And I think the BeOS port had been accepted under the same conditions
>> recently.
>
> Because we did have someone who volunteered, and because nothing would
> be lost on platforms of interest to us if the BeOS port bitrots.
Which would be also true when someone initially proposes the new "single
toolkit" port for inclusion.
>>> And I fail to see how that solves the long-term maintenance problem,
>>> once we do accept the code. This happened in the past, more than
>>> once.
>>
>> We should be able to drop unmaintained ports.
>
> Once again, a single toolkit on which all the platforms depend cannot
> be dropped. So it's a huge difference from the BeOS port.
Once again: we would only get to that point after the "single toolkit"
port is functional, accepted by the majority of us, and probably
"adopted" by a few regular contributors as their area of interest.
Only then we could realistically vote to drop all other ports.
I'm sure a contributor who would propose such new port would understand
all of this.
>> Even if we're reluctant, in general, to remove features that someone
>> is using. After all, the history of changes is saved, so as soon as
>> a volunteer arrives to resurrect it, they can start with 'git
>> revert' and continue.
>
> That's generally not a practical possibility, because the code changes
> very rapidly, and what you revert won't even compile in most cases.
Yes and no: I'm sure having the previous code available will be a lot of
help. As opposed to rewriting the same port from scratch.
next prev parent reply other threads:[~2021-12-25 12:59 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 19:19 Motif support xenodasein--- via Emacs development discussions.
2021-12-22 19:35 ` Arthur Miller
2021-12-22 19:37 ` Eli Zaretskii
2021-12-22 20:24 ` Óscar Fuentes
2021-12-23 6:42 ` Eli Zaretskii
2021-12-23 7:58 ` Arthur Miller
2021-12-23 8:55 ` Eli Zaretskii
2021-12-23 11:46 ` Arthur Miller
2021-12-23 11:52 ` Po Lu
2021-12-23 12:43 ` Arthur Miller
2021-12-23 12:52 ` Po Lu
2021-12-23 17:35 ` Arthur Miller
2021-12-24 0:38 ` Po Lu
2021-12-24 1:17 ` xenodasein--- via Emacs development discussions.
2021-12-24 1:24 ` Po Lu
2021-12-24 1:37 ` xenodasein--- via Emacs development discussions.
2021-12-24 7:24 ` Eli Zaretskii
2021-12-24 8:06 ` xenodasein--- via Emacs development discussions.
2021-12-24 8:24 ` Stefan Kangas
2021-12-24 8:37 ` Eli Zaretskii
2021-12-24 2:20 ` Stefan Kangas
2021-12-24 2:43 ` Po Lu
2021-12-24 2:59 ` [External] : " Drew Adams
2021-12-24 3:17 ` xenodasein--- via Emacs development discussions.
2021-12-24 3:26 ` Po Lu
2021-12-24 3:36 ` xenodasein--- via Emacs development discussions.
2021-12-24 7:27 ` Eli Zaretskii
2021-12-24 4:30 ` Platform independent graphical display for Emacs Stefan Kangas
2021-12-24 4:44 ` Po Lu
2021-12-24 6:28 ` Stefan Kangas
2021-12-24 6:43 ` Po Lu
2021-12-24 5:24 ` [External] : " Drew Adams
2021-12-24 7:33 ` Eli Zaretskii
2021-12-24 8:10 ` xenodasein--- via Emacs development discussions.
2021-12-24 8:41 ` Eli Zaretskii
2021-12-24 8:48 ` xenodasein--- via Emacs development discussions.
2021-12-25 0:30 ` Dmitry Gutov
2021-12-25 7:25 ` Eli Zaretskii
2021-12-25 11:23 ` Dmitry Gutov
2021-12-25 11:38 ` Eli Zaretskii
2021-12-25 11:57 ` Dmitry Gutov
2021-12-25 12:06 ` Eli Zaretskii
2021-12-25 12:59 ` Dmitry Gutov [this message]
2021-12-25 13:08 ` Eli Zaretskii
2021-12-25 12:06 ` Po Lu
2021-12-25 13:08 ` Dmitry Gutov
2021-12-25 13:36 ` Po Lu
2021-12-25 12:20 ` Óscar Fuentes
2021-12-25 12:29 ` Po Lu
2021-12-25 12:49 ` Dmitry Gutov
2021-12-25 12:54 ` Po Lu
2021-12-25 13:03 ` Dmitry Gutov
2021-12-25 13:07 ` Po Lu
2021-12-25 13:09 ` Óscar Fuentes
2021-12-25 13:20 ` Eli Zaretskii
2021-12-25 14:08 ` Óscar Fuentes
2021-12-25 14:36 ` Eli Zaretskii
2021-12-25 13:39 ` Po Lu
2021-12-25 13:44 ` xenodasein--- via Emacs development discussions.
2021-12-25 12:37 ` Eli Zaretskii
2021-12-25 13:00 ` xenodasein--- via Emacs development discussions.
2021-12-25 13:05 ` Eli Zaretskii
2021-12-25 13:11 ` xenodasein--- via Emacs development discussions.
2021-12-25 13:17 ` Óscar Fuentes
2021-12-25 13:26 ` xenodasein--- via Emacs development discussions.
2021-12-25 13:27 ` xenodasein--- via Emacs development discussions.
2021-12-25 11:51 ` Po Lu
2021-12-25 13:24 ` Dmitry Gutov
2021-12-25 13:31 ` Po Lu
2021-12-25 14:14 ` Dmitry Gutov
2021-12-25 14:30 ` Óscar Fuentes
2021-12-26 1:12 ` Po Lu
2021-12-26 1:51 ` Stefan Kangas
2021-12-26 1:56 ` Po Lu
2021-12-24 9:55 ` Lars Ingebrigtsen
2021-12-24 10:02 ` Po Lu
2021-12-24 10:16 ` Stephen Berman
2021-12-24 10:54 ` xenodasein--- via Emacs development discussions.
2021-12-24 11:07 ` Po Lu
2021-12-24 11:29 ` xenodasein--- via Emacs development discussions.
2021-12-24 11:31 ` Po Lu
2021-12-24 11:39 ` xenodasein--- via Emacs development discussions.
2021-12-24 12:08 ` Po Lu
2021-12-24 12:22 ` xenodasein--- via Emacs development discussions.
2021-12-24 12:27 ` Po Lu
2021-12-24 12:57 ` xenodasein--- via Emacs development discussions.
2021-12-24 13:09 ` Po Lu
2021-12-24 14:27 ` xenodasein--- via Emacs development discussions.
2021-12-24 16:05 ` martin rudalics
2021-12-25 0:22 ` Po Lu
2021-12-25 9:18 ` martin rudalics
2021-12-25 9:42 ` Po Lu
2021-12-26 8:25 ` martin rudalics
2021-12-26 10:16 ` Po Lu
2021-12-24 11:45 ` Óscar Fuentes
2021-12-24 12:02 ` Eli Zaretskii
2021-12-24 13:19 ` Óscar Fuentes
2021-12-24 13:26 ` Po Lu
2021-12-24 14:00 ` Óscar Fuentes
2021-12-25 0:20 ` Po Lu
2021-12-25 0:47 ` Óscar Fuentes
2021-12-25 0:57 ` Po Lu
2021-12-25 3:24 ` Jose A. Ortega Ruiz
2021-12-25 5:03 ` Po Lu
2021-12-25 5:12 ` Jose Antonio Ortega Ruiz
2021-12-25 5:23 ` Po Lu
2021-12-25 6:57 ` Eli Zaretskii
2021-12-25 9:18 ` martin rudalics
2021-12-25 5:41 ` LdBeth
2021-12-25 5:51 ` Po Lu
2021-12-24 13:42 ` Eli Zaretskii
2021-12-24 14:19 ` Óscar Fuentes
2021-12-24 11:50 ` Eli Zaretskii
2021-12-25 12:45 ` xenodasein--- via Emacs development discussions.
2021-12-24 7:17 ` Motif support Eli Zaretskii
2021-12-24 0:46 ` Po Lu
2021-12-23 15:05 ` xenodasein--- via Emacs development discussions.
2021-12-23 15:08 ` 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=6db252bf-7f0a-5c9e-544e-f2fccb488f82@yandex.ru \
--to=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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.
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).