From: Leo Famulari <leo@famulari.name>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: Rust freedom issue claim
Date: Sun, 13 Jun 2021 14:20:58 -0400 [thread overview]
Message-ID: <YMZMir2HyI2Fv3tP@jasmine.lan> (raw)
In-Reply-To: <87im2i7wb2.fsf@disroot.org>
On Sat, Jun 12, 2021 at 02:49:21PM -0400, Bone Baboon wrote:
> Contents:
> * Passive Approaches
I definitely think a passive approach is best, unless the owners of the
Rust trademark are taking actions that preclude it. Have they given us
any reason to think that we need to do something about this issue? Many
times, the best course of action is to do nothing.
next prev parent reply other threads:[~2021-06-13 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 3:24 Rust freedom issue claim Bone Baboon
2021-05-25 2:01 ` Bone Baboon
2021-05-26 14:32 ` Ludovic Courtès
2021-05-26 15:14 ` Pjotr Prins
2021-05-27 14:47 ` Joshua Branson
2021-05-27 16:28 ` Pjotr Prins
2021-05-27 20:23 ` Jack Hill
2021-06-03 18:38 ` Bone Baboon
2021-06-08 13:00 ` Ludovic Courtès
2021-06-12 18:49 ` Bone Baboon
2021-06-12 21:31 ` Vagrant Cascadian
2021-06-13 18:20 ` Leo Famulari [this message]
2021-06-15 12:38 ` Bone Baboon
2021-06-19 3:21 ` Bone Baboon
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YMZMir2HyI2Fv3tP@jasmine.lan \
--to=leo@famulari.name \
--cc=bone.baboon@disroot.org \
--cc=guix-devel@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/guix.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).