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

Re: working out where git-rebase is up to?

From
Thomas Rast <trast@student.ethz.ch>
Date
Feb 22, 2010, 10:26 UTC
Message-ID
<201002221126.47372.trast@student.ethz.ch>
In-Reply-To
<2cfc40321002220209pe1942ecucb3716f60bf05d32@mail.gmail.com>
On Monday 22 February 2010 11:09:18 Jon Seymour wrote:
Show 8 quoted lines
> Hi,
> 
> For my funky "compensating rebases" I need to know where an automated
> rebase has stopped. In particular, I need to know the sha1 of the
> commit that caused the rebase to stop.
> 
> No doubt rebase is tracking this info, but is there a supported way to
> discover it?

It's in .git/rebase-merge/done (and .git/rebase-merge/git-rebase-todo for the remaining TODO file). Maybe we should add a 'git rebase --whydiditstop' command ;-)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Marc WeberNext: Jon Seymour
Message 3 of 6 in “working out where git-rebase is up to?”
  1. Jon SeymourFeb 22, 2010
  2. Marc WeberFeb 22, 2010
  3. Thomas RastFeb 22, 2010
  4. Jon SeymourFeb 22, 2010
  5. Thomas RastFeb 22, 2010
  6. Jon SeymourFeb 22, 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.