linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: lkcl@lkcl.net
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Sun, 30 Sep 2018 16:07:48 +0200	[thread overview]
Message-ID: <8998740.bsg6g2nRDU@merkaba> (raw)
In-Reply-To: <20180930120909.30469-1-lkcl@lkcl.net>

lkcl@lkcl.net - 30.09.18, 14:09:
> > That written: Quite some of the rude mails that contained swearwords
> > I read from you have been about code, not persons. I think this is
> > an important distinction. I do not have much of an issue with
> > swearing at code :), especially when it is in some humorous way.
> 
>  absolutely, and this is one thing that a lot of people are, sadly,
>  trained pretty much from birth to be incapable of understanding:
>  namely the difference between criticism of the PERSON and criticism
>  of the ACTION.
> 
>  (1) "YOU are bad! GO STAND IN THE NAUGHTY CORNER!"
>  (2) "That was a BAD thing to do!"
>  (3) "That hurt my feelings that you did that"
> 
>  the first is the way that poorly-trained parents and kindergarten
>  teachers talk to children.
> 
>  the second is... only marginally better, but it's a start
> 
>  the third is how UNICEF trains teachers to treat children as human
> beings.

During releasing a lot of limiting "stuff" I found that probably nothing 
written or said can hurt my feelings unless I let it do so or even… 
unless I choose (!) to feel hurt about it. So at times I am clear about 
this, I´d say: "I have chosen to feel hurt about what you did."

However in this human experience a lot of people, including myself, 
still hold on to a lot of limiting "stuff" which invites feeling hurt. 
We, as humankind, have a history of hurting each other.

During this releasing work I also learned about two key ingredients of 
successful relationships: Harmlessness and mutuality. I opted out of the 
hurting cycle as best I can. And so I choose to write in a way that 
moves around what from my own experience of feeling hurt I know could 
hurt others. I choose to write in a harmless way so to say. While still 
aiming to bring my point across. A very important ingredient for this is 
to write from my own experience. 

Of course others can feel hurt about something I would not feel hurt 
about and I may not be aware that the other might feel hurt about. That 
is why in such a case it is important to give and receive feedback. 
Still when writing from my own experience without saying that anything 
is wrong with the other, it appears to be unlikely to trigger hurt. That 
is at least my experience so far.

Thanks,
-- 
Martin



  reply	other threads:[~2018-09-30 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 19:22 Linux 4.19-rc4 released, an apology, and a maintainership note Linus Torvalds
2018-09-16 21:42 ` [...] " Adam Borowski
2018-09-16 23:59   ` Moritz Obermeier
2018-09-17  0:18 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17  0:20 ` [...] " Andy Isaacson
2018-09-17  0:23 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17  6:57 ` opal hart
2018-09-17  7:57 ` […] " Martin Steigerwald
2018-09-17  8:53   ` Martin Steigerwald
2018-09-30 12:09     ` Re: Linux 4.19-rc4 released, " lkcl
2018-09-30 14:07       ` Martin Steigerwald [this message]
2018-09-30 16:27         ` Luke Kenneth Casson Leighton
2018-09-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches
2018-09-17 21:09 ` Michael Woods
2018-09-18  1:30   ` Pavel Snajdr
2018-09-21 22:13     ` Michael Woods
2018-10-04 14:57     ` Eric W. Biederman
2018-10-08 15:29       ` Enrico Weigelt, metux IT consult
2018-10-08 13:54     ` Enrico Weigelt, metux IT consult
2018-10-08 16:36 ` Enrico Weigelt, metux IT consult
2018-09-17  2:15 Luke Kenneth Casson Leighton
2018-09-18  2:10 ` Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton

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=8998740.bsg6g2nRDU@merkaba \
    --to=martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcl@lkcl.net \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).