git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	 Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>,
	 git@vger.kernel.org,  Brian Lyles <brianmlyles@gmail.com>,
	 Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] rebase: apply and cleanup autostash when rebase fails to start
Date: Wed, 14 Aug 2024 10:27:29 -0700	[thread overview]
Message-ID: <xmqq8qwzypz2.fsf@gitster.g> (raw)
In-Reply-To: <b676bd17-1cc8-4639-acb7-675dde32a1ae@gmail.com> (Phillip Wood's message of "Wed, 14 Aug 2024 16:59:32 +0100")

Phillip Wood <phillip.wood123@gmail.com> writes:

> Applying the stash should not fail because the rebase has not started
> and so HEAD, the index and the worktree are unchanged since the stash
> was created. If it does fail for some reason then apply_autostash()
> creates a new entry under refs/stash. We definitely do want to remove
> the directory otherwise we're left with the inconsistent state we're
> tying to fix.

If it is not expected to fail 99% of times, it feels more prudent to
abort loudly without making further damage to lose information and
ask the user to check what happened in the working tree, rather than
blindly removing the clue to understand what went wrong.  For
example, could the reason why applying the stash failed be because
the user forgot that the working tree was being used for rebasing
and mucked with its contents from say another terminal?

Thanks.

  reply	other threads:[~2024-08-14 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 13:22 [PATCH] rebase: apply and cleanup autostash when rebase fails to start Phillip Wood via GitGitGadget
2024-08-14 14:36 ` Patrick Steinhardt
2024-08-14 15:59   ` Phillip Wood
2024-08-14 17:27     ` Junio C Hamano [this message]
2024-08-15  9:47       ` Phillip Wood
2024-09-08 21:54         ` Junio C Hamano
2024-09-08 21:54         ` Junio C Hamano
2024-09-02 15:12 ` [PATCH v2] " Phillip Wood via GitGitGadget
2024-09-08 21:55   ` Junio C Hamano
2024-09-12 20:44     ` 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=xmqq8qwzypz2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=brianmlyles@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --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 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).