{"thread":{"id":"65568","subject":"git interactive rebase does not allow editing commits at once anymore","startedAt":"2026-04-30T07:46:08Z","lastAt":"2026-04-30T13:43:48Z","messageCount":3,"participants":["David Jordanes","Junio C Hamano","Phillip Wood"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"542518","messageId":"DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com","threadId":"65568","inReplyTo":null,"subject":"git interactive rebase does not allow editing commits at once anymore","fromName":"David Jordanes","fromEmail":"davidjordanes@outlook.com","sentAt":"2026-04-30T07:46:05Z","receivedAt":"2026-04-30T07:46:08Z","isPatch":false,"body":"Git version: git version 2.53.0.windows.2\nOS: Windows 11\n\nSteps to reproduce:\n1. Create a dummy repo\n2. Create a couple of commits\n2. Run git rebase -i HEAD~2\n\nObserved:\nLines in todo appear as:\npick <hash> # commit 1\npick <hash> # commit 2\n\nAfter editing:\nreword <hash> commit A\nreword <hash> commit B\n\nThen git loops each commit to edit. \n\nExpected:\nAfter editing, all changes should be applied at once (no loop).\n\nQuestion:\nIs this intended behavior? By whom and why this flow was decided? What problem it solves? If I have to rebase interactively 10 or 15 commits I have to go through all those commits one by one???"},{"id":"542521","messageId":"xmqqo6j0zthw.fsf@gitster.g","threadId":"65568","inReplyTo":"DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com","subject":"Re: git interactive rebase does not allow editing commits at once anymore","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-04-30T09:29:15Z","receivedAt":"2026-04-30T09:29:18Z","isPatch":false,"body":"David Jordanes <davidjordanes@outlook.com> writes:\n\n> Git version: git version 2.53.0.windows.2\n> OS: Windows 11\n\nI do not do Windows, but I am curious about \"anymore\" part of your\nmessage title.  Are you reporting a regression?\n"},{"id":"542531","messageId":"986ca9b2-2ad1-4b2e-a61f-3407fe5d5251@gmail.com","threadId":"65568","inReplyTo":"DB7PR03MB3881199B8D12CC7A981ADF0CA8352@DB7PR03MB3881.eurprd03.prod.outlook.com","subject":"Re: git interactive rebase does not allow editing commits at once anymore","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2026-04-30T13:43:44Z","receivedAt":"2026-04-30T13:43:48Z","isPatch":false,"body":"Hi David\n\nOn 30/04/2026 08:46, David Jordanes wrote:\n> Git version: git version 2.53.0.windows.2\n> OS: Windows 11\n> \n> Steps to reproduce:\n> 1. Create a dummy repo\n> 2. Create a couple of commits\n> 2. Run git rebase -i HEAD~2\n> \n> Observed:\n> Lines in todo appear as:\n> pick <hash> # commit 1\n> pick <hash> # commit 2\n> \n> After editing:\n> reword <hash> commit A\n> reword <hash> commit B\n> \n> Then git loops each commit to edit.\n\nIf you mean git opens the editor for you to edit the first commit \nmessage and then when you close the editor it opens the second message, \nit is working as it always has done. There is an external program called \n\"git-revise\" which I believe lets you edit multiple commit message at \nonce though I've not used it myself.\n\nProcessing the commits one at a time lets you inspect the changes for \nthe commit you're editing the message for and if you have \n\"commit.verbose\" enabled then git will show you the diff for the commit \nbelow the commit message in the editor.\n\nThanks\n\nPhillip\n\n\n> Expected:\n> After editing, all changes should be applied at once (no loop).\n> \n> Question:\n> Is this intended behavior? By whom and why this flow was decided? What problem it solves? If I have to rebase interactively 10 or 15 commits I have to go through all those commits one by one???\n\n"}]}