From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@klomp.org
Cc: gcc@gcc.gnu.org, luke.leighton@gmail.com
Subject: Re: rust non-free-compatible trademark
Date: Sun, 17 Jul 2022 19:55:44 EDT [thread overview]
Message-ID: <20220717235544.D82EE33CAC@vlsi1.gnat.com> (raw)
In-Reply-To: <YtSUagpJh6cXcBq7@wildebeest.org>
> Normal use of a word isn't something that Trademarks prevent.
In general, no, but what it prevents is using the word in a way that
would produce confusion with an "official" use of that mark. If the
word that constitutes the mark is too general, then the trademark
shouldn't have been granted. But let's assume that somebody has
trademarked a common adjective, which we'll call "adjective", when
applied to noun "noun".
If I write "I have an adjective noun", that's supposed to refer to the
trademarked it. If it instead refers to some other item (e.g., in our
case a compiler with patches), that's a trademark violatio.
next prev parent reply other threads:[~2022-07-17 23:55 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
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 [this message]
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=20220717235544.D82EE33CAC@vlsi1.gnat.com \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=luke.leighton@gmail.com \
--cc=mark@klomp.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.
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).