From: Thierry Reding <thierry.reding@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: b4 shazam --continue
Date: Fri, 21 Oct 2022 17:44:51 +0200 [thread overview]
Message-ID: <Y1K+czGJHoCd/4z6@orome> (raw)
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
Hi Konstantin,
when I apply a patch or series and midway some error occurs (could be
checkpatch or conflict, for example) shazam will interrupt the operation
and drop me to a shell. I can then resolve whatever errors those are and
resume using git am --continue, but that has the side-effect of loosing
track of the patch/series. Things like added Link: tags still work, but
thankyous are no longer tracked.
I've gone through the documentation and various b4 threads on this list
but haven't found any solution to this. Is there a way to have shazam
pick up where it left off? Or would it be possible to add such a
mechanism?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-10-21 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 15:44 Thierry Reding [this message]
2022-10-24 21:19 ` b4 shazam --continue Konstantin Ryabitsev
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=Y1K+czGJHoCd/4z6@orome \
--to=thierry.reding@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).