git_range_to_patches: add git options to better represent renames and copies
Get series with b4
b4 am [email protected] change-id 20250705-format-harder-e6ebba524bc1Versions newest first
- v2 Latest2 patches 2 repliesIn review
- 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 files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | git_range_to_patches: add git options to better represent renames and copiessrc/ | +4 | 0 replies | |
| 2/2 | git_range_to_patches: set minimum similarity index to 95%src/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
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]>