threads / discuss / 35659

After stash pop, refs/stash become 40 zeroes

Subject: After stash pop, refs/stash become 40 zeroes

## tl;dr

3 messages between Jan 15, 2014 and Jan 15, 2014.

replies: 2people: 2as markdown or json

乙酸鋰· Jan 15, 2014, 05:56 UTC · lore
Hi,

what are the possible causes of this? After stash pop, refs/stash becomes 40 zeroes. This is the only stash, so refs/stash should be deleted after pop. However, it becomes 40 zeroes.

git 1.8.x
乙酸鋰· Jan 15, 2014, 06:00 UTC · re: 乙酸鋰 · lore

Re: After stash pop, refs/stash become 40 zeroes

Also, logs/refs/stash becomes empty (0 bytes of file size) after pop.
2014/1/15 乙酸鋰 <ch3cooli@gmail.com>:
Show 8 quoted lines
> Hi,
>
> what are the possible causes of this?
> After stash pop, refs/stash becomes 40 zeroes.
> This is the only stash, so refs/stash should be deleted after pop.
> However, it becomes 40 zeroes.
>
> git 1.8.x
Jeff King· Jan 15, 2014, 08:51 UTC · re: 乙酸鋰 · lore

Re: After stash pop, refs/stash become 40 zeroes

On Wed, Jan 15, 2014 at 01:56:52PM +0800, 乙酸鋰 wrote:
Show 6 quoted lines
> what are the possible causes of this?
> After stash pop, refs/stash becomes 40 zeroes.
> This is the only stash, so refs/stash should be deleted after pop.
> However, it becomes 40 zeroes.
> 
> git 1.8.x
I can't reproduce the problem here. Running this:
  git init -q repo && cd repo
  echo content >file && git add file && git commit -qm file
  echo more >>file
  echo "==> stashed"
  git stash -q
  ls -l .git/refs/stash .git/logs/refs/stash
  git rev-parse --verify refs/stash
  echo "==> popped"
  git stash pop -q
  ls -l .git/refs/stash .git/logs/refs/stash
  git rev-parse --verify refs/stash
yields:
  ==> stashed
  -rw-r--r-- 1 peff peff 153 Jan 15 03:49 .git/logs/refs/stash
  -rw-r--r-- 1 peff peff  41 Jan 15 03:49 .git/refs/stash
  7fb40812ac4aaf7fa31e584863fc52c4b4a67aa0
  ==> popped
  ls: cannot access .git/refs/stash: No such file or directory
  ls: cannot access .git/logs/refs/stash: No such file or directory
  fatal: Needed a single revision

Does running it reproduce the problem for you? If it does, can you be more specific about your git version? If it does not, can you show what you are doing differently to reproduce?

-Peff

← back to recent threads