public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: lkcl <luke.leighton@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: David Brown <david.brown@hesbynett.no>,
	GCC developers <gcc@gcc.gnu.org>,  Mark Wielaard <mark@klomp.org>
Subject: Re: rust non-free-compatible trademark
Date: Mon, 18 Jul 2022 10:06:57 +0100	[thread overview]
Message-ID: <CAPweEDxYBUcxQLriyBkPDGJi8tS7=ZjGu5NhG33vO7CmfqRfYQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQJ4J8VTVXjbRDmOZ3Hqm56TAcVJ1iSL9WdGdkG4s2UhQ@mail.gmail.com>

On Mon, Jul 18, 2022 at 9:50 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:

> You haven't been ignored. People have expressed reasonable
> disagreements with your interpretation.
>
> Just because every line of your email hasn't been explicitly responded
> to with positive acknowledgement of receipt doesn't mean you've been
> ignored.

if i feel that i've been ignored, and it makes me upset and frustrated
i have every right to say so, and whilst i know that you are trying to
help you are unfortunately at risk from telling me that my feelings
are invalid, which is a line that i trust you understand is completely
and utterly inappropriate that you cannot cross.

bottom line is that you're giving a perfectly reasonable justification
for Mark's lack of empathy.

[sadly this is extremely common in Technical discussions]

i know exactly what Mark's doing: he's only superficially skim-reading
reading (citing the Java case without even acknowledging that i'd
raised it already - twice), wants to take control of the conversation and
wants it shut down as quickly as possible (telling me to "go contact the
Rust Foundation directly").

i'd very much like to see Mark read - and follow - this
https://www.crnhq.org/cr-kit/#empathy

i'm already at this:
https://www.crnhq.org/cr-kit/#assertiveness

l.

  reply	other threads:[~2022-07-18  9: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
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 [this message]
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='CAPweEDxYBUcxQLriyBkPDGJi8tS7=ZjGu5NhG33vO7CmfqRfYQ@mail.gmail.com' \
    --to=luke.leighton@gmail.com \
    --cc=david.brown@hesbynett.no \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@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).