git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git interactive rebase 'consume' command

From
SKStephen Kelly <steveire@gmail.com>
Date
Jan 21, 2013, 08:40 UTC
Message-ID
<kdiuu0$bvt$1@ger.gmane.org>
In-Reply-To
<7v8v7nli2a.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Stephen Kelly <steveire@gmail.com> writes:
Show 11 quoted lines
>> One scenario is something like this:
>>
>>  Start with a clean HEAD (always a good idea :) )
>>  hack hack hack
>>  make multiple commits
>>  realize that a hunk you committed in an early patch belongs in a later
>>  one. use git rebase -i to fix it.
>>
>> Is that more clear?
> 
> Not really.
I think there are other scenarios, but I guess this won't happen anyway.
Thanks,
Steve.
Previous: Jeff KingNext: Michael Haggerty
Message 8 of 10 in “git interactive rebase 'consume' command”
  1. Stephen KellyJan 20, 2013
  2. John KeepingJan 20, 2013
  3. Stephen KellyJan 20, 2013
  4. Junio C HamanoJan 20, 2013
  5. Stephen KellyJan 20, 2013
  6. Junio C HamanoJan 20, 2013
  7. Jeff KingJan 21, 2013
  8. Stephen KellyJan 21, 2013
  9. Michael HaggertyJan 21, 2013
  10. Stephen KellyJan 21, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.