13 ms·

Sure, so BFG/filter-branch/rebase on a NEW branch, that can't affect existing developers, then automate cherry-picking `master` <=> `new-master`, get all develo

by tln 8y ago

Sure, so BFG/filter-branch/rebase on a NEW branch, that can't affect existing developers, then automate cherry-picking `master` <=> `new-master`, get all developers to switch at their own pace... Good point on log/blame/annotate.

WorldMaker 8y ago
"automate cherry-picking" is where I feel the migraine starts in git. I've seen three-way merge hell and it starts with something like that.