From: lkcl <luke.leighton@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC developers <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Sun, 17 Jul 2022 17:47:20 +0100 [thread overview]
Message-ID: <CAPweEDyhFvy_EvyDBxCpGni=uO_1Kwfunvtx3_ijkNMc6fk2DA@mail.gmail.com> (raw)
In-Reply-To: <6F935597-82AE-4128-B282-BE714E02B683@gmail.com>
On Sun, Jul 17, 2022 at 5:25 PM Richard Biener
<richard.guenther@gmail.com> wrote:
> > if the word "rust" is entirely removed from the gcc source code then
> > there is no problem whatsoever (recall: "iceweasel").
>
> We’ll call it gust.
love it! the puns i would have recommended would have been based
on "iron oxide".
please bear in mind: under Trademark Law, as developers, you *must* not make
"announcements" saying "we *are* changing the name from rust to gust".
this creates "Confusion" for which you become directly and legally liable
and responsible.
*users* are permitted to go, "oh look, errr there's this thing called gust
and the source code compiles for rust".
just as with the Java Trademark, you as developers can say "gust is
compatible with
the rust language" but you *cannot* say "gust is compatible with rust".
Trademarks are a bitch. get legal advice.
l.
next prev parent reply other threads:[~2022-07-17 16:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 15:28 lkcl
2022-07-17 16:25 ` Richard Biener
2022-07-17 16:47 ` lkcl [this message]
2022-07-17 18:24 ` Richard Kenner
2022-07-17 18:57 ` Alexandre Oliva
2022-07-17 16:31 ` Mark Wielaard
2022-07-17 17:06 ` lkcl
2022-07-17 17:41 ` Mark Wielaard
2022-07-17 18:11 ` lkcl
2022-07-17 18:29 ` lkcl
2022-07-17 22:59 ` Mark Wielaard
2022-07-17 23:07 ` lkcl
2022-07-17 23:55 ` Richard Kenner
2022-07-17 18:28 ` Richard Kenner
2022-07-17 18:54 ` Alexandre Oliva
2022-07-18 7:09 ` David Brown
2022-07-18 8:07 ` lkcl
2022-07-18 8:50 ` Jonathan Wakely
2022-07-18 9:06 ` lkcl
2022-07-18 14:30 ` lkcl
2022-07-18 17:11 ` Richard Kenner
2022-07-18 17:12 ` Richard Kenner
2022-07-18 18:32 ` Florian Weimer
2022-07-18 18:43 ` Arthur Cohen
2022-07-19 9:43 ` Florian Weimer
2022-07-18 19:35 ` lkcl
2022-07-18 21:01 ` David Malcolm
2022-07-18 23:09 ` lkcl
2022-07-19 9:27 ` Gabriel Ravier
2022-07-19 10:26 ` lkcl
2022-07-19 10:55 ` Jonathan Wakely
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDyhFvy_EvyDBxCpGni=uO_1Kwfunvtx3_ijkNMc6fk2DA@mail.gmail.com' \
--to=luke.leighton@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@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.
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).