From: Andrew Cooper <andrew.cooper3@citrix.com>
To: tools@linux.kernel.org
Subject: b4 shazam in a subdir
Date: Tue, 2 May 2023 18:06:15 +0100 [thread overview]
Message-ID: <4e4757cf-7351-9aff-fada-2b03ff82b2dc@citrix.com> (raw)
Hello,
When using b4 shazam in a subdir of a git repository, you end up with
the patch(es) applied correctly, but also the diff structure expanded
under the current dir, and the working tree dirty back to the state
prior to applying the patch(es).
Running from the root of the repo leaves everything in order, but it
would be great if b4 wasn't sensitive to $CWD inside a repository.
Thanks,
~Andrew
next reply other threads:[~2023-05-02 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 17:06 Andrew Cooper [this message]
2023-05-02 17:13 ` b4 shazam in a subdir Konstantin Ryabitsev
2023-05-02 17:18 ` Kernel.org Bugbot
2023-06-22 20:21 ` Kernel.org Bugbot
2023-06-30 12:35 ` andrew.cooper3
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=4e4757cf-7351-9aff-fada-2b03ff82b2dc@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=tools@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).