From: Thomas Rast <trast@student.ethz.ch>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: working out where git-rebase is up to?
Date: Mon, 22 Feb 2010 11:26:47 +0100 [thread overview]
Message-ID: <201002221126.47372.trast@student.ethz.ch> (raw)
In-Reply-To: <2cfc40321002220209pe1942ecucb3716f60bf05d32@mail.gmail.com>
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
next prev parent reply other threads:[~2010-02-22 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 10:09 working out where git-rebase is up to? Jon Seymour
2010-02-22 10:19 ` Marc Weber
2010-02-22 10:26 ` Thomas Rast [this message]
2010-02-22 10:47 ` Jon Seymour
2010-02-22 10:49 ` Thomas Rast
2010-02-22 10:51 ` Jon Seymour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201002221126.47372.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jon.seymour@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).