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

Re: Can't get git rebase --onto to work

From
DDavid <bouncingcats@gmail.com>
Date
Jun 2, 2011, 11:18 UTC
Message-ID
<BANLkTi=P_-XbmeJiUs2FaEfXLksKM6jRgw@mail.gmail.com>
In-Reply-To
<BANLkTik-o=h05=d5JH_LirYQkNzgdYaZxg@mail.gmail.com>
On 2 June 2011 20:58, Howard Miller <howard@e-learndesign.co.uk> wrote:
Show 10 quoted lines
>
> The examples are very helpful but it could be a little more explicit
> which branches are going to get modified by the rebase. Once there are
> several branches in play it becomes quite a hard think.
>
> Mostly, I just needed a kick to say "look where the branch heads are
> pointing" (in the example diagrams) before and after the rebase. I
> don't think I would have got it without the remark in Pro Git that a
> final merge is required to get the HEADs where I wanted them. Like
> most things - it's completely obvious when you know.

If you have a graphical environment, it might help to take a look with 'gitk --all'. Also, if you start it before the rebase, then after the rebase you will need to use its "File>Reload" command to refresh the display.

Previous: Howard MillerNext: Tim Guirgies
Message 8 of 10 in “Can't get git rebase --onto to work”
  1. Howard MillerJun 2, 2011
  2. Carlos Martín NietoJun 2, 2011
  3. Howard MillerJun 2, 2011
  4. Tim GuirgiesJun 2, 2011
  5. Howard MillerJun 2, 2011
  6. Tim GuirgiesJun 2, 2011
  7. Howard MillerJun 2, 2011
  8. DavidJun 2, 2011
  9. Tim GuirgiesJun 2, 2011
  10. Howard MillerJun 2, 2011

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.