public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Corporate affiliations of Council members
Date: Wed, 24 Jun 2020 22:22:28 +0200	[thread overview]
Message-ID: <e574d9df-a403-b794-629b-3d9f2316b2c9@gentoo.org> (raw)
In-Reply-To: <41946474.2IY78Rhhic@farino>

On 2020-06-24 22:08, Andreas K. Hüttel wrote:
> Am Mittwoch, 24. Juni 2020, 22:30:08 EEST schrieb Patrick Lauer:
>>
>> So, uhm.
>> I'll let you claim it was late and the beer was talking.
>>
>> But that's a totally incoherent hallucination you're projecting on me.
>>
> [...]
>>
>> Your hallucination that we don't update things is fascinating, but not
>> based on any observations.
>>
> 
> It's based on my observations of your Gentoo contributions.
> If the code quality at work is the same as in Gentoo, then nothing is updated.
> 

Sigh.

You're /really/ aiming low these days.

So just for the record -

I've been a bit less active in gentoo land because my son had leukemia.

In February he had his immune system rebooted with a stem cell 
transplant, so he's in a reasonably good state now.

As you may or may not be able to imagine this has been slightly 
stressful and time-consuming.


I don't like to bring my personal troubles into the public sphere, but 
claiming I'm lazy when you're very aware of the situation is quite 
exquisitely rude. You should feel bad.

The shitty discussion style on the mailing lists has motivated me to not 
actively engage in discussions, because within about 30 minutes we're 
bikeshedding ad hominems instead of having a meaningful conversation.
It's just horribly tedious and unproductive, but "we've always done it 
like this" etc.etc.


I wonder if all y'all communicate like this at work, or if Gentoo is the 
safe space where you can let out all the frustrations ...

Anyway. Enough said.

May you dream of being happy.

Good night,

Patrick


  reply	other threads:[~2020-06-24 20:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 16:18 [gentoo-project] Corporate affiliations of Council members Michał Górny
2020-06-22 17:07 ` Brian Dolbec
2020-06-22 17:36 ` Robin H. Johnson
2020-06-22 18:20   ` Rich Freeman
2020-06-22 18:15 ` Matt Turner
2020-06-22 18:56 ` Alec Warner
2020-06-22 20:17   ` Michał Górny
2020-06-23 21:17   ` Andreas K. Hüttel
2020-06-24  5:53     ` Michał Górny
2020-06-24 11:23       ` Rich Freeman
2020-06-22 19:36 ` Ulrich Mueller
2020-06-22 20:32 ` William Hubbs
2020-06-23 13:33 ` Thomas Deutschmann
2020-06-23 17:48 ` Patrick Lauer
2020-06-23 20:50   ` Andreas K. Hüttel
2020-06-24 19:30     ` Patrick Lauer
2020-06-24 20:00       ` David Seifert
2020-06-24 20:08       ` Andreas K. Hüttel
2020-06-24 20:22         ` Patrick Lauer [this message]
2020-06-26 13:39           ` Andreas K. Huettel
2020-06-23 21:02 ` Andreas K. Hüttel
2020-06-26  1:41 ` Max Magorsch
2020-06-26  3:23 ` Aaron Bauman
2020-06-27 13:51 ` Mikle Kolyada
2020-06-28 19:57 ` Georgy Yakovlev
  -- strict thread matches above, loose matches on Subject: below --
2020-07-02 17:14 Richard Yao

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=e574d9df-a403-b794-629b-3d9f2316b2c9@gentoo.org \
    --to=patrick@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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