From: Taylan Kammer <taylan.kammer@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: guix-devel@gnu.org
Subject: Re: Accusation of breach of CoC (Was: [minor patch] Amend CoC)
Date: Thu, 24 Feb 2022 15:19:40 +0100 [thread overview]
Message-ID: <843aa5cc-6ae4-4bdf-d4c3-bf395a021625@gmail.com> (raw)
In-Reply-To: <X1q2pJu4USakYZQyKlduFUVZSSiIiDh_GWthWfovB0tMb8VmjgMzYUEnzdwwTwETOWbx7OSkSKJQS7N6frasUkFi-_phcMi0Stb1hw_7qxE=@elenq.tech>
On 24.02.2022 14:21, Ekaitz Zarraga wrote:
>
>> I suspect you haven't properly read any of my mails and jumped to conclusions
>> based on a quick skim, or something like that.
>
> Well, I've been reading them and some people told you to stop and you still
> continue. People already told you were bothering them.
I haven't posted anything after Andy and Oliver asked to take it off-list,
other than responding to Blake's accusation of course.
Before that, nobody told me to stop or that I was bothering them, unless I
missed it?
--
Taylan
next prev parent reply other threads:[~2022-02-24 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 11:38 [minor patch] Amend CoC Blake Shaw
2022-02-24 13:05 ` Accusation of breach of CoC (Was: [minor patch] Amend CoC) Taylan Kammer
2022-02-24 13:21 ` Ekaitz Zarraga
2022-02-24 14:19 ` Taylan Kammer [this message]
2022-02-25 19:42 ` An appeal to empathy on actual hurt caused by this thread Christine Lemmer-Webber
2022-02-25 23:40 ` Morgan Lemmer Webber
2022-02-26 4:03 ` Taylan Kammer
2022-02-26 4:14 ` Christine Lemmer-Webber
2022-02-26 11:35 ` Ekaitz Zarraga
2022-02-26 15:39 ` Morgan Lemmer Webber
2022-02-26 19:07 ` Christine Lemmer-Webber
2022-02-28 22:24 ` Taylan Kammer
2022-02-28 22:52 ` Ekaitz Zarraga
2022-02-28 23:03 ` Christine Lemmer-Webber
2022-03-01 0:12 ` Ludovic Courtès
2022-03-01 2:39 ` Maxim Cournoyer
2022-03-01 3:00 ` Tobias Geerinckx-Rice
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=843aa5cc-6ae4-4bdf-d4c3-bf395a021625@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=ekaitz@elenq.tech \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.