git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "mattjackets" <mattlist@fastmail.fm>
To: git@vger.kernel.org
Subject: Stash missing, but not.  Can apply, but not drop or list the stash.
Date: Tue, 23 Sep 2008 17:23:01 -0400	[thread overview]
Message-ID: <1222204981.28575.1275592473@webmail.messagingengine.com> (raw)

I have a strange stash problem.  There is a single stash in the repo.

git stash apply 0  --  works, but results in a conflict.  Lets just go
ahead and drop the stash...

git stash list  --  shows nothing.  huh?  Lets go ahead with the drop
anyway and hope it works...

$ git stash drop stash@{0}
fatal: Log .git/logs/refs/stash is empty.
stash@{0}: not a valid stashed state

sure enough, .git/logs/refs/stash is empty

git stash clear  --  does nothing

I'm at a loss.  I can apply the stash cleanly to older revisions, and
gitk still shows the stash branch.  How can I fix this?  is it safe to
simply delete the stash branch as if it was any other branch?

Thanks,
Matt
-- 
  matt
  mattlist@fastmail.fm

-- 
http://www.fastmail.fm - Access all of your messages and folders
                          wherever you are

             reply	other threads:[~2008-09-23 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 21:23 mattjackets [this message]
2008-09-23 23:08 ` Stash missing, but not. Can apply, but not drop or list the stash Brandon Casey
2008-09-23 23:57   ` [PATCH maint] git-stash.sh: don't default to refs/stash if invalid ref supplied Brandon Casey
2008-10-01 19:53     ` regression: stash show -p (was [PATCH maint] git-stash.sh: don't default to refs/stash if invalid ref supplied) Brandon Casey
2008-10-02 23:52       ` [PATCH] git-stash.sh: fix flawed fix of invalid ref handling (commit da65e7c1) Brandon Casey

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=1222204981.28575.1275592473@webmail.messagingengine.com \
    --to=mattlist@fastmail.fm \
    --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).