From: Fiona Behrens <me@kloenk.dev>
To: tools@kernel.org
Subject: b4: wrong base-branch in non commit tracking info
Date: Sat, 22 Feb 2025 01:12:46 +0100 [thread overview]
Message-ID: <87eczqygzl.fsf@kloenk.dev> (raw)
Hi,
I'm currently trying a bit with adding a git notes based cover letter
strategy. While working on that I found that if the cover letter
strategy is not commit, and the user preps a new series with a fork
point (-f) the current branch that is checked out is tracked as base-branch,
even if current commits do not appear in the fork point.
Didn't yet understand the prep base code sufficent to directly send a
patch.
I'm not yet sure how well a notes based cover letter stragety will work
and want to test it before sending a patch, but the current WIP branch
is in my git[0]
Thanks,
Fiona
[0]: https://cyberchaos.dev/kloenk/b4/-/commits/cover-strategy-notes
reply other threads:[~2025-02-22 0:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87eczqygzl.fsf@kloenk.dev \
--to=me@kloenk.dev \
--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;
as well as URLs for NNTP newsgroup(s).