{"thread":{"id":"22624","subject":"[RFC] git rebase --edit","startedAt":"2010-02-12T08:44:26Z","lastAt":"2010-02-12T09:29:18Z","messageCount":2,"participants":["Tay Ray Chuan","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134296","messageId":"be6fef0d1002120044w5f14d061t52863fbc8b0bd304@mail.gmail.com","threadId":"22624","inReplyTo":null,"subject":"[RFC] git rebase --edit","fromName":"Tay Ray Chuan","fromEmail":"rctay89@gmail.com","sentAt":"2010-02-12T08:44:26Z","receivedAt":"2010-02-12T08:44:26Z","isPatch":false,"sender":{"key":"rctay89@gmail.com","avatar":"https://avatars.githubusercontent.com/u/61553?v=4"},"body":"Hi,\n\nsometimes, I need to edit a commit, and I find myself doing some\nrather \"mechanical\" steps.\n\n  $ git log #find the commit\n  $ git rebase -i <commit>^\n  $ #mark <commit> with 'e', save, exit editor\n\n  Stopped at <commit>... <commit message>\n  You can amend the commit now, with\n  ...\n\nPerhaps git-rebase --interactive could learn an option, say, --edit\n<commit>, that\n\n  1. determines where to start the rebase (instead of saying <commit>^ above),\n  2. marks <commit> as 'e' in git-rebase-todo,\n  3. start the edit process (\"You can amend the commit now...\").\n\nThe user would then proceed with the usual git-rebase --continue.\n\nIs this a workable suggestion?\n\n-- \nCheers,\nRay Chuan\n"},{"id":"134301","messageId":"alpine.DEB.1.00.1002121026380.20986@pacific.mpi-cbg.de","threadId":"22624","inReplyTo":"be6fef0d1002120044w5f14d061t52863fbc8b0bd304@mail.gmail.com","subject":"Re: [RFC] git rebase --edit","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2010-02-12T09:29:18Z","receivedAt":"2010-02-12T09:29:18Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 12 Feb 2010, Tay Ray Chuan wrote:\n\n> [description how to amend a single commit that is not HEAD]\n>\n> Perhaps git-rebase --interactive could learn an option, say, --edit\n> <commit>, that\n> \n>   1. determines where to start the rebase (instead of saying <commit>^ above),\n>   2. marks <commit> as 'e' in git-rebase-todo,\n>   3. start the edit process (\"You can amend the commit now...\").\n> \n> The user would then proceed with the usual git-rebase --continue.\n> \n> Is this a workable suggestion?\n\nSure!\n\nNote that the current workflow for such things is to make a temporary \ncommit which is then handled by the new \"fixup\" command. But of course, \nthis only works if your history is not messy, i.e. has too many changes in \nthe same place (because then the fixup commit does not apply cleanly to \nthe commit in question).\n\nCiao,\nDscho\n"}]}