Why not make all the edits in one pass? It just looks horrendous. I wonder though, is there a git history fixer out there somewhere that rewrites history to merge commits with the same message into one?
Rebase isn't at all slow. I know this because I do it often to squash my own commits or move things around between branches.
> Nah, rebase is too slow on large histories and it might not be your own commit which complicates things.
I don't see any questions being asked. Rebase on the commits we're discussing (readme tweaks) are trivial: fixup fixup fixup
Read the thread next time. I started by asking if there's a fixer and then someone suggests a single command that absolutely doesn't solve the problem and would take enormous time to use on some projects, even more so if your PC isn't the best of the best.
Are you thinking about rebasing through an IDE? IDEs are uniformly terrible at git.
I am not thinking about rebasing trough an IDE. Try rebasing in Chromium's repository, it's simply not fast. The thing I asked for is something that would auto-fix the entire commit histories in cases such as the Requests repository, the suggested use of rebase is too tedious and slow. Has something still remained unclear?
The intent for a tool which could do this quickly is unclear. Rebasing millions of commits will be slow, also rebasing published history will also generate a lot of extra paperwork.
Writing a utility to sort a rebase todo by message and change the later commits with the same message to be fixups is trivial.
That doesn’t apply in this case, though, where the README is markdown
rst may be less popular than md but there's no shortage of local preview options, including plugins/extensions for popular editors.