git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: 乙酸鋰 <ch3cooli@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: After stash pop, refs/stash become 40 zeroes
Date: Wed, 15 Jan 2014 03:51:39 -0500	[thread overview]
Message-ID: <20140115085139.GA14335@sigill.intra.peff.net> (raw)
In-Reply-To: <CAHtLG6TmkYdGRF3H-6CoVvnxZqZBBk3ZUR-ohTVvgeAe9tTuOA@mail.gmail.com>

On Wed, Jan 15, 2014 at 01:56:52PM +0800, 乙酸鋰 wrote:

> 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

      parent reply	other threads:[~2014-01-15  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  5:56 After stash pop, refs/stash become 40 zeroes 乙酸鋰
2014-01-15  6:00 ` 乙酸鋰
2014-01-15  8:51 ` Jeff King [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=20140115085139.GA14335@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=ch3cooli@gmail.com \
    --cc=git@vger.kernel.org \
    /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).