Re: working out where git-rebase is up to?
- From
Jon Seymour <jon.seymour@gmail.com>
- Date
- Feb 22, 2010, 10:47 UTC
- Message-ID
- <2cfc40321002220247q1b73ac32v6ff39035a61a6a1@mail.gmail.com>
- In-Reply-To
- <201002221126.47372.trast@student.ethz.ch>
Once I am done with my compensating rebase, rebase won't have to stop :-)
jon.
On Mon, Feb 22, 2010 at 9:26 PM, Thomas Rast <trast@student.ethz.ch> wrote:
Show 18 quoted lines
> On Monday 22 February 2010 11:09:18 Jon Seymour wrote:
>> 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
>