From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: b4 bug: "Error tagging the revision" in project with git submodules
Date: Mon, 28 Jul 2025 10:09:49 -0400 [thread overview]
Message-ID: <20250728-bald-wise-bison-febf6e@lemur> (raw)
In-Reply-To: <CAAjaMXYtY62_KeEbshWA4vjhtUzNgTO0wffcZXNy95EqvL+Ovg@mail.gmail.com>
On Mon, Jul 28, 2025 at 03:01:51PM +0300, Manos Pitsidianakis wrote:
> Hello,
>
> When doing `b4 send` on the QEMU project, all works well except
> tagging the revision fails, I assume because the temporary git
> worktree doesn't have all submodules (perhaps some of them have not
> been "update"d to be fetched locally?)
Okay, I was never really happy with the way I implemented this via tagging, so
this may be the reason for me to get back and review how it's done.
Thanks for the report.
bugspray tag me
next prev parent reply other threads:[~2025-07-28 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 12:01 b4 bug: "Error tagging the revision" in project with git submodules Manos Pitsidianakis
2025-07-28 14:09 ` Konstantin Ryabitsev [this message]
2025-07-28 14:15 ` Bugspray Bot
2025-08-20 14:58 ` Manos Pitsidianakis
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=20250728-bald-wise-bison-febf6e@lemur \
--to=konstantin@linuxfoundation.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=tools@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