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

Re: Why can't git-rebase back up?

From
Junio C Hamano <junkio@cox.net>
Date
Feb 18, 2006, 07:39 UTC
Message-ID
<7vmzgpru8m.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060217135938.7412.qmail@science.horizon.com>
linux@horizon.com writes:
Show 9 quoted lines
> But suppose discover a nasty bug in -rc3 and want to move my build branch
> back to -rc2.  "git-rebase v2.6.16-rc2" does nothing.  After a bit
> of thought, I realize why, but sometime I do want to back up.
>
> What's the best way to do that?  Should git-rebase take an optional
> third argument which is the branch head we are moving away from?
> E.g. what I want to do would be
>
> 	git-rebase v2.6.16-rc2 build v2.6.16-rc3
The one in "next" has a topic branch change which lets you say:
	$ git rebase --onto v2.6.16-rc2 v2.6.16-rc3 build
which is a shorthand for
	$ git checkout build
	$ git rebase --onto v2.6.16-rc2 v2.6.16-rc3

That is, tear out my changes that forked from the development trail that led to v2.6.16-rc3, and graft them on top of v2.6.16-rc2.

Previous: Junio C HamanoNext: linux@horizon.com
Message 6 of 10 in “Why can't git-rebase back up?”
  1. linux@horizon.comFeb 17, 2006
  2. Andreas EricssonFeb 17, 2006
  3. linux@horizon.comFeb 17, 2006
  4. Andreas EricssonFeb 17, 2006
  5. Junio C HamanoFeb 18, 2006
  6. Junio C HamanoFeb 18, 2006
  7. linux@horizon.comFeb 18, 2006
  8. Junio C HamanoFeb 18, 2006
  9. linux@horizon.comFeb 18, 2006
  10. Johannes SchindelinFeb 18, 2006

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.