From: "René Scharfe" <l.s.r@web.de>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>,
Marek Mrva <mrva@eof-studios.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [bug] Stashes lost after out-of-memory situation
Date: Sun, 25 Oct 2020 16:42:20 +0100 [thread overview]
Message-ID: <22f34328-1e87-aa4b-3893-564dff1fb893@web.de> (raw)
In-Reply-To: <5a3db65b-1877-c5be-8077-2926637fba6e@virtuell-zuhause.de>
Am 25.10.20 um 13:27 schrieb Thomas Braun:
> On 10/24/2020 7:06 PM, René Scharfe wrote:
>
> [...]
>
>> Looks like stash calls rev-parse to see if a
>> stash pop removed the last stash and in that case proceeds to delete the
>> stash ref and its reflog
>
> I was a bit suprised to learn that removing the last stash entry also
> removes it from the reflog.
>
> Wouldn't it be more convenient if it would be kept in the reflog even
> after popping?
The log of the stash ref is separate from the normal reflog. Popping
a stash doesn't remove anything from the latter.
René
prev parent reply other threads:[~2020-10-25 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 14:53 [bug] Stashes lost after out-of-memory situation Marek Mrva
2020-10-24 17:06 ` René Scharfe
2020-10-25 12:27 ` Thomas Braun
2020-10-25 15:42 ` René Scharfe [this message]
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=22f34328-1e87-aa4b-3893-564dff1fb893@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mrva@eof-studios.com \
--cc=thomas.braun@virtuell-zuhause.de \
/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).