From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Hahler <git@thequod.de>
Subject: Re: [PATCH] rebase -i: restore autostash on abort
Date: Tue, 28 Jun 2016 12:02:22 -0700 [thread overview]
Message-ID: <xmqqa8i587cx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160628175704.26095-1-ps@pks.im> (Patrick Steinhardt's message of "Tue, 28 Jun 2016 19:57:04 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> When we abort an interactive rebase we do so by calling
> `die_abort`, which cleans up after us by removing the rebase
> state directory. If the user has requested to use the autostash
> feature, though, the state directory may also contain a reference
> to the autostash, which will now be deleted.
>
> Fix the issue by trying to re-apply the autostash in `die_abort`.
> This will also handle the case where the autostash does not apply
> cleanly anymore by recording it in a user-visible stash.
I do not do autostash myself, but it is a good thing to try not to
lose information ;-)
> +test_expect_success 'restore autostash on editor failure' '
> + test_when_finished "git reset --hard" &&
> + echo uncommited-content >file0 &&
> + (
> + test_set_editor "false" &&
> + test_must_fail git rebase -i --autostash HEAD^
> + ) &&
> + echo uncommited-content >expected &&
While making sure this case works is crucial, it is not an
interesting failure mode, is it? Can we also have "does not apply
cleanly anymore" case, too?
> + test_cmp expected file0
> +'
> +
> test_done
next prev parent reply other threads:[~2016-06-28 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 17:57 [PATCH] rebase -i: restore autostash on abort Patrick Steinhardt
2016-06-28 19:02 ` Junio C Hamano [this message]
2016-06-28 20:42 ` Matthieu Moy
2016-06-28 21:13 ` Junio C Hamano
2016-06-29 6:28 ` Patrick Steinhardt
2016-06-29 6:21 ` [PATCH v2] " Patrick Steinhardt
2016-06-29 14:02 ` Johannes Schindelin
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=xmqqa8i587cx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@thequod.de \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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.