From: Mikhail Kryshen <mikhail@kryshen.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: conflicts in the gnu project now affect guile
Date: Thu, 17 Oct 2019 21:11:48 +0300 [thread overview]
Message-ID: <871rvbp7h7.fsf@e6230.localdomain> (raw)
In-Reply-To: <87blugg7dt.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Andy,
If you've long had issues with RMS, then why do you still want to be
with GNU? You don't have to participate in GNU to be part of the free
software movement. Is it that you see GNU as an important platform for
your political activism? Is it about donations? Identity? Pride?
What is it so significant that it made you stoop to harassment and
defamation? Or could it be that you act purely on emotion under
influence of the widespread moral panic?
You are trying to publicly destroy a person for his opinions that you
chose to interpret in the most unfavorable way possible. But consider
that your interpretations are wrong — just the possibility of it makes
your actions totally morally unacceptable.
I respect you as a programmer and contributor to free software, but this
act of yours is a severe disgrace.
--
Mikhail
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2019-10-17 18:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:14 conflicts in the gnu project now affect guile Andy Wingo
2019-10-16 14:11 ` Thompson, David
2019-10-16 15:33 ` Christopher Lemmer Webber
2019-10-16 16:10 ` Eli Zaretskii
2019-10-19 17:05 ` Mark H Weaver
2019-10-16 18:27 ` Jean Louis
2019-10-16 18:27 ` Jean Louis
2019-10-16 19:30 ` pelzflorian (Florian Pelz)
2019-10-18 9:44 ` Alex Sassmannshausen
2019-10-16 18:12 ` Jean Louis
[not found] ` <CAGua6m3d_t2hd7P2ueTsPZytF7pNO7f8xptBWofPw9UvyYWDaw@mail.gmail.com>
2019-10-16 21:32 ` Fwd: " Stefan Israelsson Tampe
2019-10-16 21:56 ` Tadeus Prastowo
2019-10-16 22:05 ` Adrienne G. Thompson
2019-10-18 3:16 ` Richard Stallman
2019-10-18 3:17 ` Richard Stallman
2019-10-18 10:37 ` Tadeus Prastowo
2019-10-16 19:21 ` Mikael Djurfeldt
2019-10-16 21:03 ` Linus Björnstam
2019-10-17 0:18 ` Arne Babenhauserheide
2019-10-17 1:24 ` Mark H Weaver
2019-10-17 7:07 ` Jan Nieuwenhuizen
2019-10-18 7:24 ` Mark H Weaver
2019-10-19 7:51 ` Guile and Mes [WAS: conflicts in the gnu project now affect guile] Jan Nieuwenhuizen
2019-10-19 8:56 ` Mikael Djurfeldt
2019-10-18 11:20 ` conflicts in the gnu project now affect guile Christopher Lemmer Webber
2019-10-18 13:14 ` Mark H Weaver
2019-10-18 13:33 ` Christopher Lemmer Webber
2019-10-18 13:49 ` Thompson, David
2019-10-17 1:40 ` Mike Gran
2019-10-17 2:11 ` Neil Van Dyke
2019-10-17 18:11 ` Mikhail Kryshen [this message]
2019-10-18 9:26 ` Alex Sassmannshausen
2019-10-19 4:03 ` Mikhail Kryshen
2019-10-18 1:06 ` Mark H Weaver
2019-10-18 6:31 ` Nala Ginrut
2019-10-18 9:20 ` Mikael Djurfeldt
2019-10-18 14:22 ` Ludovic Courtès
2019-10-19 22:55 ` Taylan Kammer
2019-10-20 3:08 ` Mark H Weaver
2019-10-20 3:54 ` Nala Ginrut
2019-10-20 19:12 ` Taylan Kammer
-- strict thread matches above, loose matches on Subject: below --
2019-10-18 11:29 Todor Kondić
2019-10-18 15:09 ` pelzflorian (Florian Pelz)
2019-10-18 11:45 Mark H Weaver
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rvbp7h7.fsf@e6230.localdomain \
--to=mikhail@kryshen.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).