From: lkcl <luke.leighton@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: GCC developers <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Mon, 18 Jul 2022 00:07:20 +0100 [thread overview]
Message-ID: <CAPweEDx5VUvW9mZO-AP4gUpVD7ixh6Fx6RivwdHSf9_6o4fZvA@mail.gmail.com> (raw)
In-Reply-To: <YtSUagpJh6cXcBq7@wildebeest.org>
sorry, Mark, you're still misunderstanding, on multiple levels
and in so many ways i am having a hard time tracking them
all.
i don't feel that i've been heard, and consequently do not
feel comfortable continuing the conversation, especially
given that i have other priorities.
if you had asked questions "so let me make sure that
i understand you correctly" i would feel much more
comfortable to continue the conversation.
i have raised the topic: it is your responsibility and duty to
consider.
l.
next prev parent reply other threads:[~2022-07-17 23:07 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 [this message]
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=CAPweEDx5VUvW9mZO-AP4gUpVD7ixh6Fx6RivwdHSf9_6o4fZvA@mail.gmail.com \
--to=luke.leighton@gmail.com \
--cc=gcc@gcc.gnu.org \
--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).