From: Markus Armbruster <armbru@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Kyle Evans" <kevans@freebsd.org>,
"Stacey Son" <sson@freebsd.org>
Subject: Re: [PATCH] bsd-user: Switch to SPDX-License-Expression
Date: Thu, 05 Mar 2026 07:16:46 +0100 [thread overview]
Message-ID: <87342e94xd.fsf@pond.sub.org> (raw)
In-Reply-To: <CANCZdfrgcpVN+MzNCCkVTFa8-Y2G-ajwqJHk4K0OuKvzot=Qeg@mail.gmail.com> (Warner Losh's message of "Tue, 3 Mar 2026 09:41:15 -0700")
Warner Losh <imp@bsdimp.com> writes:
[...]
> I'm trying to not let my irritation show through too much, but I'm only 10k
> lines into 40k of upstreaming and these side trips are slowing things down
> too much. I appreciate the reviews that have found bugs in the code, but
> I'm struggling with requests like this. I really need to limit the scope of
> what I take on because there's a lot left to do and I'm doing it in my
> spare time.
>
> So does that sound like a good plan? Or what should I do?
>
> Warner
>
> P.S. Sorry if my frustration is showing through too much...
I don't see a reason for apologies here.
Cooperation gets frustrating at times. We may hide our frustration,
stew in it until it becomes unbearable, then explode, or give up and go
away. All undesirable outcomes. It's better to be open about it early,
in a respectful manner. This is what you did, and it's alright.
It's okay to say "no, because" to reviewer requests. We can then try to
work out a path forward together.
next prev parent reply other threads:[~2026-03-05 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 4:46 [PATCH] bsd-user: Switch to SPDX-License-Expression Warner Losh
2026-03-03 8:51 ` Daniel P. Berrangé
2026-03-03 12:17 ` Warner Losh
2026-03-03 12:52 ` Daniel P. Berrangé
2026-03-03 16:41 ` Warner Losh
2026-03-05 6:16 ` Markus Armbruster [this message]
2026-03-05 18:04 ` Warner Losh
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=87342e94xd.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=sson@freebsd.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 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.