Skip to content

git_range_to_patches: add git options to better represent renames and copies

Jens Glathe b4-sent tools 2 versions – In review

Get series with b4
b4 am [email protected] change-id 20250705-format-harder-e6ebba524bc1

Versions newest first

  1. v2 Latest2 patches 2 repliesIn review
  2. v11 patch 0 repliesSuperseded

Changes in v2 from the cover letter

- set minimum similarity index to 95% to avoid un-reviewable patches
- Link to v1: https://patch.msgid.link/[email protected]

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2git_range_to_patches: add git options to better represent renames and copiessrc/b4/__init__.py+4 -00 replies
2/2git_range_to_patches: set minimum similarity index to 95%src/b4/__init__.py+1 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH b4 v2 0/2] git_range_to_patches: add git options to better represent renames and copies

This is an attempt at mitigating the real-world issue of file renames in patches due to code restructuring. I have a few of these, and would like to keep using b4 for patch management.

---
Changes in v2:
- set minimum similarity index to 95% to avoid un-reviewable patches
- Link to v1: https://patch.msgid.link/[email protected]

---
Jens Glathe (2):
git_range_to_patches: add git options to better represent renames and copies
git_range_to_patches: set minimum similarity index to 95%

 src/b4/__init__.py | 4 ++++
 1 file changed, 4 insertions(+)

---
base-commit: a9b2aba54be85ea2933c43b8a6d71c1611230b59
change-id: 20250705-format-harder-e6ebba524bc1

Best regards,

Signature · 1 line
Jens Glathe <[email protected]>