From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, emacs-devel@gnu.org
Subject: Re: Consideration for Rust contributions in Emacs
Date: Sat, 15 Apr 2023 11:40:40 +0800 [thread overview]
Message-ID: <87ttxhizif.fsf@yahoo.com> (raw)
In-Reply-To: <E1pnWiG-0005a0-Qq@fencepost.gnu.org> (Richard Stallman's message of "Fri, 14 Apr 2023 23:36:32 -0400")
Richard Stallman <rms@gnu.org> writes:
> But we need to keep focus on the aspects of this policy which are
> worse than merely irritating. The adoption of this policy would make
> the unmodified Rust compiler source code nonfree unless we devise a
> way to remove all uses of the trademark, as trademark law understands
> the concept.
>
> How MUCH alterattion that would require, and how much work that would
> be, I am not sure. Would a global replace of `rust' with `lust' in
> the source files of the Rust compiler suffice? It would include a
> similar renaming of source file names. It would not be the minimal
> possible change as measured by diff, but it might be the change that
> is the least work.
I don't know.
> One would have the installation script create a symlink or alias from
> /usr/bin/rust to /usr/bin/lust. Trademark law, from what lawyers have
> told me, covers communications to human beings, not commands for
> programs.
>
> Pu Lu, can you find places where discussion of this is happening, and
> tell us?
`Po Lu' please, thanks.
Unfortunately, I can't really follow these issues. I have no idea where
this discussion is happening.
I wonder how GCC will deal with these issues, seeing as a Rust compiler
is already part of GCC.
next prev parent reply other threads:[~2023-04-15 3:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f2ee2f1d-332f-4707-bd9e-23444c34749f@Spark>
2023-01-21 22:48 ` Consideration for Rust contributions in Emacs Troy Hinckley
2023-01-22 7:44 ` Po Lu via Emacs development discussions.
2023-01-22 11:05 ` Daniel Martín
2023-01-22 14:04 ` Po Lu
2023-01-22 23:16 ` Troy Hinckley
2023-01-23 5:55 ` Po Lu
2023-01-24 3:49 ` Richard Stallman
2023-01-24 3:52 ` Richard Stallman
2023-01-24 6:52 ` Dr. Arne Babenhauserheide
2023-01-23 2:00 ` Sean Allred
2023-01-23 3:37 ` Troy Hinckley
2023-01-23 12:25 ` Po Lu
2023-01-24 2:24 ` Lynn Winebarger
2023-01-24 2:47 ` Etienne Prud'homme
2023-01-24 2:49 ` Po Lu
2023-04-11 12:39 ` Po Lu via Emacs development discussions.
2023-04-11 18:23 ` Dr. Arne Babenhauserheide
2023-04-15 3:36 ` Richard Stallman
2023-04-15 3:40 ` Po Lu [this message]
2023-04-15 7:03 ` Eli Zaretskii
2023-04-12 0:36 ` Dmitry Gutov
2023-04-12 4:59 ` tomas
2023-04-12 11:26 ` Richard Stallman
2023-04-13 1:02 ` Richard Stallman
2023-04-13 5:09 ` Eli Zaretskii
2023-04-13 8:23 ` Po Lu
2023-04-15 23:27 ` Dmitry Gutov
2023-04-16 0:11 ` Po Lu
2023-04-17 2:55 ` Richard Stallman
2023-01-23 13:21 ` Dr. Arne Babenhauserheide
2023-01-23 16:51 ` John Yates
2023-01-23 17:06 ` Eli Zaretskii
2023-01-23 18:22 ` John Yates
2023-01-23 19:04 ` Eli Zaretskii
2023-01-23 19:44 ` Bob Rogers
2023-01-23 19:56 ` Eli Zaretskii
2023-01-23 20:08 ` Bob Rogers
2023-01-23 19:22 ` Dr. Arne Babenhauserheide
2023-01-23 23:52 ` Po Lu
2023-01-24 0:45 ` Po Lu
2023-01-23 7:32 ` Robert Pluim
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=87ttxhizif.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=arne_bab@web.de \
--cc=emacs-devel@gnu.org \
--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 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).