From: Andrew Wong <andrew.kw.w@gmail.com>
To: Alexander Kostikov <alex.kostikov@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Rebase doesn't restore branch pointer back on out of memory
Date: Thu, 04 Oct 2012 18:52:23 -0400 [thread overview]
Message-ID: <506E1327.1070602@gmail.com> (raw)
In-Reply-To: <CAGAhT3k=T0SGngMQkbXHqNfh-=LUb71C7CSrWXP2wsAgc8Tb8A@mail.gmail.com>
On 10/04/2012 05:09 PM, Alexander Kostikov wrote:
> Full script is uploaded to
> https://dl.dropbox.com/u/10828740/rebase.log Here is the last page:
Judging from that log, I'm pretty sure "rebase" is failing at
"format-patch". I was able to reproduce the issue you're having:
"rebase" finished and modified the branch even though it actually failed.
"rebase" is not catching that error. I'll try to come up with a patch to
fix it later tonight, so that "rebase" will fail correctly. And when it
does, you'll be able to do "rebase --abort" to go back to your original
state.
next prev parent reply other threads:[~2012-10-04 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 19:47 Rebase doesn't restore branch pointer back on out of memory Alexander Kostikov
2012-10-03 21:52 ` Andrew Wong
[not found] ` <CAGAhT3mVn-W5P-n_YeafZ_7bntkJGArJ3o6+dA5GO_H44=KHFg@mail.gmail.com>
2012-10-04 15:13 ` Andrew Wong
2012-10-04 21:09 ` Alexander Kostikov
2012-10-04 21:39 ` Alexander Kostikov
2012-10-04 22:52 ` Andrew Wong [this message]
2012-10-04 23:59 ` Alexander Kostikov
2012-10-05 4:53 ` Andrew Wong
2012-10-05 4:53 ` [RFC] rebase: Handle cases where format-patch fails Andrew Wong
2012-10-05 20:17 ` Junio C Hamano
2012-10-08 19:36 ` Andrew Wong
2012-10-08 19:36 ` Andrew Wong
2012-10-08 22:38 ` Junio C Hamano
2012-10-11 3:54 ` Rebase doesn't restore branch pointer back on out of memory Andrew Wong
2012-10-11 3:54 ` [PATCH] rebase: Handle cases where format-patch fails Andrew Wong
2012-10-19 21:49 ` Rebase doesn't restore branch pointer back on out of memory Alexander Kostikov
2012-10-19 22:24 ` Junio C Hamano
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=506E1327.1070602@gmail.com \
--to=andrew.kw.w@gmail.com \
--cc=alex.kostikov@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.