From: Przemek Kitszel <[email protected]> Date: Tue, 15 Jul 2025 22:33:40 +0200 > Hi, > > I have developed (or discovered ;)) how to split a file in a way that > both old and new are nice in terms of git-blame > > https://github.com/pkitszel/linux/commits/virtchnl-split/ > > The purpose of RFC is to ask if anyone is in strong disagreement with me > > There is more commits needed to have it nice, so it forms a git-log vs > git-blame tradeoff, but (after the brief moment that this is on the top) > we spend orders of magnitude more time looking at the blame output (and > commit messages linked from that) - so I find it much better to see > actual logic changes instead of "move xx to yy" stuff (typical for > "squashed/single-commit splits").
FWIW, git-blame has -M/C to track X-times line moves within/across files. > > Cherry-picks/rebases work the same with this method as with simple > "squashed/single-commit" approach (literally all commits squashed into > one (to have better git-log, but shitty git-blame output). > > Rationale for the split itself is, as usual, "file is big and we want to > extend it". >
