From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Anastasia Belova <abelova@astralinux.ru>,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] afs: Fix overwriting of result of DNS query
Date: Thu, 21 Dec 2023 10:01:32 -0800 [thread overview]
Message-ID: <CAHk-=wjJtcyi=oRf7Rtf2RueWq_336KEsSf9b-BKPxRcHHQx+Q@mail.gmail.com> (raw)
In-Reply-To: <1842328.1703171371@warthog.procyon.org.uk>
On Thu, 21 Dec 2023 at 07:09, David Howells <dhowells@redhat.com> wrote:
>
> Could you apply this fix, please?
Ok, so this is just *annoying*.
Why did you send me this as a patch, and then *twenty minutes* later
you send me an AFS pull request that does *not* include this patch?
WTF?
I've applied this, but I'm really annoyed, because it really feels
like you went out of your way to just generate unnecessary noise and
pointless workflow churn.
It's not even like the pull request contained anything different. The
patch _and_ the pull request were both not just about AFS, but about
DNS issues in AFS.
Get your act together.
Linus
next prev parent reply other threads:[~2023-12-21 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:09 [PATCH] afs: Fix overwriting of result of DNS query David Howells
2023-12-21 18:01 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 14:23 David Howells
2023-12-21 14:30 ` Jeffrey E Altman
2023-12-21 14:50 ` Jeffrey E Altman
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='CAHk-=wjJtcyi=oRf7Rtf2RueWq_336KEsSf9b-BKPxRcHHQx+Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=abelova@astralinux.ru \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=marc.dionne@auristor.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 NNTP newsgroup(s).