From: Thomas Gummerer <t.gummerer@gmail.com>
To: Marce Romagnoli <marce.romagnoli@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Fwd: `git stash pop -q` is deleting files.
Date: Tue, 17 Dec 2019 13:59:45 +0000 [thread overview]
Message-ID: <20191217135945.GA5103@cat> (raw)
In-Reply-To: <CA+0NiBGQHK_bVdH11zRErxNTjvyU-SqJYj=CHZy3afm47+reYA@mail.gmail.com>
[please don't top-post on this list]
On 12/17, Marce Romagnoli wrote:
> But it seems is still happening to me in 2.24.1 -latest-
It being in master doesn't mean it has made it into a release yet,
though it means it will in the future. So you have a couple of
options in the meantime:
- Compile Git yourself from the 'master' branch
- Go back to an older version of git. v2.23 didn't have this
problem, but it had a different issue that I was trying to fix in
34933d0eff ("stash: make sure to write refreshed cache",
2019-09-11), but where this bug was introduced.
- set the stash.useBuiltin configuration option to false, which will
make you use the legacy stash written as a shell script. This
also shouldn't have this bug.
> El lun., 16 dic. 2019 a las 20:13, Junio C Hamano
> (<gitster@pobox.com>) escribió:
> >
> > I think this has already been fixed with
> >
> > http://lore.kernel.org/git/20191113150136.GB3047@cat
> >
> > at the tip of 'master' a few weeks ago.
> >
next prev parent reply other threads:[~2019-12-17 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+0NiBEFssPJsQ8UV6vRNBxzUEsJddF4Q-=-xVq-xgNUtFbHUA@mail.gmail.com>
[not found] ` <CA+0NiBGcYwu1Gyyv3AQEbfQCMiE0rrurzgkQzwsjHgi9cEj4wQ@mail.gmail.com>
[not found] ` <CA+0NiBFU46YRBFEbngK+Rc0e4uE_nSqQkYak9a-_UoTaCCb1Jg@mail.gmail.com>
2019-12-16 13:19 ` Fwd: `git stash pop -q` is deleting files Marce Romagnoli
2019-12-16 19:13 ` Junio C Hamano
2019-12-17 13:32 ` Marce Romagnoli
2019-12-17 13:59 ` Thomas Gummerer [this message]
2019-12-17 16:10 ` Marce Romagnoli
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=20191217135945.GA5103@cat \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marce.romagnoli@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 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.