rt-tests: patches rename & versoin bump & support of non-NPTL tools
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/4] rt-tests: patches rename & versoin bump & support of non-NPTL tools
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hi,
Quoted 2 lines
I must confess that I don't actually don't know precisely how git encodes renames. But basically, my understanding is that even if you do
Easy, it doesn't. It just stores blobs and the old and new files will share the same blob as they are identical. The rename detection is only for how you want the commit to PRESENTED.
Quoted 7 lines
"git mv", "git format-patch" will encode a rename as a complete removal
+ a complete addition, because that's the only way, in the traditional patch format, to express a rename. However, by passing -M to git format-patch, you tell git that it can generate a git patch, making the assumption that it's git that will be used to apply the patch, and not just the basic "patch" tool. In this case, it can encode the rename in a smarter way.
Indeed. You can enable it by default with something like:
git config --global diff.renames copy
Signature · 1 line
Bye, Peter Korsgaard