Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <cover.1687802358.git.dsterba@suse.com>
In-Reply-To: <cover.1687802358.git.dsterba@suse.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 26 Jun 2023 11:49:13 -0700
Message-ID: <CAHk-=wgAxb2PQiAp5eKQmZd1=7DLA60O=+=Y3xcsvDa-N6Y+NA@mail.gmail.com>
Subject: Re: [GIT PULL] Btrfs updates for 6.5
To:     David Sterba <dsterba@suse.com>
Cc:     linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, 26 Jun 2023 at 11:21, David Sterba <dsterba@suse.com> wrote:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.5

Ouch. I did this merge twice.

Your pull request only points to the branch. I didn't immediately
notice - my scripting only complains about non-kernel.org addresses -
but then after doing the merge I went "Hmm, I see no signature".

And then I noticed that you do have a for-6.5-tag that points to your
branch, you just didn't mention it in the pull request.

So then I re-did it all.

Can I ask you to be more careful in your pull request flow, and point
at the tag? I did notice eventually, and I'll go make my scripting
actually complain even about kernel.org pulls without signed tags so
that I'll notice earlier (and not just by mistake when I happen to
check later)

                Linus