From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 6.5
Date: Mon, 26 Jun 2023 21:04:15 +0200 [thread overview]
Message-ID: <20230626190415.GZ16168@suse.cz> (raw)
In-Reply-To: <CAHk-=wgAxb2PQiAp5eKQmZd1=7DLA60O=+=Y3xcsvDa-N6Y+NA@mail.gmail.com>
On Mon, Jun 26, 2023 at 11:49:13AM -0700, Linus Torvalds wrote:
> 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)
I'm sorry about that, I had to redo the pull request before sending and
did not update the tag name in the new cover letter, it's not
automated/scripted on my side. I'll go fix it now.
next prev parent reply other threads:[~2023-06-26 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 18:14 [GIT PULL] Btrfs updates for 6.5 David Sterba
2023-06-26 18:49 ` Linus Torvalds
2023-06-26 19:04 ` David Sterba [this message]
2023-06-26 20:02 ` pr-tracker-bot
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=20230626190415.GZ16168@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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