From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: /me taps out
Date: Mon, 27 Sep 2021 19:35:15 -0700 [thread overview]
Message-ID: <20210928023515.GH570642@magnolia> (raw)
Hi folks,
Between this and last week's conference and meeting activities, I have
experienced so much pressure and stress dealing with discussions that
never seem to resolve, preparing for customer meetings where people
complain about why can't I get things moving faster, and feeling under
the gun to squeeze patches onto the list in between everything else
going on to try to keep other people unblocked (hence the RFC-for-people
patchsets last week) that I've turned into That Jerk on IRC.
I apologize for being the roaring jerk to people and am putting myself
on timeout until at least next Tuesday the 5th. I hope this will ease
off by then, because I need to stop working successive 12 hour days.
--D
reply other threads:[~2021-09-28 2:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210928023515.GH570642@magnolia \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.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