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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx> wrote:
> 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
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]