From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: luangruo@yahoo.com, comms@dabrev.com, allred.sean@gmail.com,
emacs-devel@gnu.org
Subject: Re: Consideration for Rust contributions in Emacs
Date: Thu, 13 Apr 2023 08:09:36 +0300 [thread overview]
Message-ID: <83h6tk5pwv.fsf@gnu.org> (raw)
In-Reply-To: <E1pmlLu-00033f-T2@fencepost.gnu.org> (message from Richard Stallman on Wed, 12 Apr 2023 21:02:18 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: comms@dabrev.com, allred.sean@gmail.com, emacs-devel@gnu.org
> Date: Wed, 12 Apr 2023 21:02:18 -0400
>
> What you've sent is very alarming. I need to study the whole thin.
> Pu Lu, would you please send me the URL of the document you are looking at?
> Also, what is its title, and whose statement is it?
Since Po Lu didn't respond, I assume he has email delivery problems
again, and will respond in his stead.
The URL where you can find this document is:
https://docs.google.com/document/d/1ErZlwz9bbSI43dNo-rgQdkovm2h5ycuW220mWSOAuok/edit
https://docs.google.com/document/d/1ErZlwz9bbSI43dNo-rgQdkovm2h5ycuW220mWSOAuok/edit#heading=h.3znysh7
The title is "Rust Trademark Policy". Don't know a formal answer to
the "whose statement is it" part, but the announcement requests that
feedback and questions be sent to trademark@rustfoundation.org.
> Also, if you can tell, when was it published?
Two days ago.
next prev parent reply other threads:[~2023-04-13 5:09 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
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 [this message]
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=83h6tk5pwv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=allred.sean@gmail.com \
--cc=comms@dabrev.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 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).