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

Re: [PATCH] rebase--interactive: don't enforce valid branch

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 15, 2010, 17:14 UTC
Message-ID
<7vbpepse17.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.DEB.2.00.1003150132060.4362@narbuckle.genericorp.net>
Dave Olszewski <cxreg@pobox.com> writes:
Show 16 quoted lines
>> Also I did't follow the code, but does it behave sanely when you say
>> "rebase --abort"?
>
> Good question.  It turns out that both rebase and rebase -i will end
> up on the commit specified by <branch>, whether it's a branch or not.
> That might be the expected and desired behavior, though:
>
>   [Starting on branch A]
>   git rebase origin/B B
>   git rebase --abort
>   [HEAD is now a symref to B]
>
>   [Starting on branch A]
>   git rebase origin/B B^0
>   git rebase --abort
>   [HEAD is now detached at B^0]
Yup, that is what I would call "behave sanely".  Thanks for clarification.
Previous: Dave Olszewski
Message 8 of 8 in “rebase--interactive: don't enforce valid branch”
  1. rebase--interactive: don't enforce valid branchDave Olszewski, Mar 15, 2010
  2. Junio C HamanoMar 15, 2010
  3. Dave OlszewskiMar 15, 2010
  4. Junio C HamanoMar 15, 2010
  5. Dave OlszewskiMar 15, 2010
  6. Junio C HamanoMar 15, 2010
  7. Dave OlszewskiMar 15, 2010
  8. Junio C HamanoMar 15, 2010

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.