3 ms·
OK, I see your original comment, no need to be rude. If you're working on a computer that struggles with 'making a commit' and 'editing a text file', I feel lik
by falsedan 7y ago
OK, I see your original comment, no need to be rude. If you're working on a computer that struggles with 'making a commit' and 'editing a text file', I feel like you're working in an environment that's going to be very frustrating when writing code.
Are you thinking about rebasing through an IDE? IDEs are uniformly terrible at git.
- Avamander 7y agoI just don't like downvotes because people take comments out of context. 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?
- _-___________-_ 7y agoLate to the party, but it would be trivial to use `git rebase -i` and a decent editor to fix the Requests commit history. I just gave it a go locally and got good results with less than a minute's editing.
- falsedan 7y ago> Try rebasing in Chromium's repository, it's simply not fast 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.