From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Android port (was: gnulib fsusage)
Date: Fri, 20 Jan 2023 09:47:34 +0300 [thread overview]
Message-ID: <Y8o5BkadOR3huUZW@protected.localdomain> (raw)
In-Reply-To: <831qnqppkm.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2023-01-19 17:28]:
> > From: Po Lu <luangruo@yahoo.com>
> > Cc: emacs-devel@gnu.org
> > Date: Thu, 19 Jan 2023 21:40:18 +0800
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > I didn't just read your request, I've looked at the branch. I'm not
> > > sure I'm happy with what I see there. Too much stuff that IMNSHO
> > > should have been discussed before coding it.
> >
> > Could you please explain what that would be?
> > This seems like a good opportunity to start discussing it now, thanks.
>
> First, we need to decide whether we indeed want to have this in Emacs.
> Android is not a free platform, so when its support comes with a lot
> of additional non-trivial code that we'd need to understand and
> support/maintain (including a lot of Java), we had better discussed
> that first.
Replicant is free platform.
Replicant:
https://www.replicant.us/
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-20 6:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bkmv6z36.fsf.ref@yahoo.com>
2023-01-19 2:24 ` gnulib fsusage Po Lu
2023-01-19 6:44 ` Eli Zaretskii
2023-01-19 8:52 ` Michael Albinus
2023-01-19 10:11 ` Po Lu
2023-01-19 10:26 ` Eli Zaretskii
2023-01-19 11:59 ` Po Lu
2023-01-19 13:33 ` Eli Zaretskii
2023-01-19 13:40 ` Po Lu
2023-01-19 14:27 ` Android port (was: gnulib fsusage) Eli Zaretskii
2023-01-19 14:34 ` Android port Po Lu
2023-01-19 14:56 ` Eli Zaretskii
2023-01-20 0:18 ` Po Lu
2023-01-20 7:09 ` Eli Zaretskii
2023-01-20 9:39 ` Po Lu
2023-01-25 10:48 ` Po Lu
2023-01-26 8:59 ` Eli Zaretskii
2023-01-20 6:47 ` Jean Louis [this message]
2023-01-20 7:19 ` Android port (was: gnulib fsusage) Eli Zaretskii
2023-01-28 7:50 ` Konstantin Kharlamov
2023-01-28 8:49 ` Eli Zaretskii
2023-01-28 9:06 ` Konstantin Kharlamov
2023-01-28 9:21 ` Eli Zaretskii
2023-01-28 9:31 ` Konstantin Kharlamov
2023-01-28 9:59 ` Android port Po Lu
2023-01-29 9:54 ` Android port (was: gnulib fsusage) Jean Louis
2023-01-28 9:57 ` Android port Po Lu
2023-01-28 10:23 ` Konstantin Kharlamov
2023-01-29 9:38 ` Android port (was: gnulib fsusage) Jean Louis
2023-01-29 20:36 ` 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=Y8o5BkadOR3huUZW@protected.localdomain \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).