I initially raised this as a FR with my git UI of choice, and was told that it was actually something that git itself would need to do ... and that the standard way to raise Feature Requests was to email this list. Apologies if that's not actually what I should be doing - please let me know if this is not an intended use. =-=-=-=-=-=-=-=-=-= When you do an interactive rebase, you are presented with a file listing all the commit hashes, their current message, and the command/operation to perform. To edit the commit message you set operation `r` and then are later given the opportunity to set the message. But that control file is only using the commit hashes to determine which commit is being referenced - the message text in that file isn't being used to identify the message. So can we allow the user to (optionally) set the new message directly in that file? It would make the flow a lot quicker (don't have to open a new editor instance each time.), and would make it a lot easier to make similar changes to a bunch of commits (e.g. prefixing them all with Ticket number, or fixing a consistent typo in a bunch of commits.) Indicator that the commit-rename should use the text in the control file (rather than the later editor prompt) could either be A) a new command (rename-inline, or similar) or B) existing rename command + "the text on this line is different from the text on the original commit". Obviously this wouldn't support multiline commit messages - those would still use the existing workflow, but adding this new feature wouldn't impinge upon them, so they've not lost anything. Am happy to suggest names and/or shorthand keys for it, if the idea is acceptable. Yours, Brondahl
