git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: xuinkrbin <nabble.20.xuinkrbin@spamgourmet.com>
To: git@vger.kernel.org
Subject: While the awesome switch is always on, so is the confusion switch.
Date: Tue, 4 May 2010 08:17:25 -0700 (PDT)	[thread overview]
Message-ID: <28447763.post@talk.nabble.com> (raw)


Hi, All!

So, here's the situation.  I start with no modifications to HEAD and no
stashes.  I verify the lack of stashes with a 'git stash list'.  I make some
changes so I now have modifications to HEAD and, still, no stashes.  I
verify the lack of stashes with a 'git stash list'.  I run 'git stash' so I
now have no modifications to but a stash.  I verify the presence of a stash
with a 'git stash list'.  I run 'git stash pop' so I now have modifications
to head but no stashes.  I run 'git stash list' to verify the lack of
stashes and receive the following message:
	fatal: bad object refs/stash
If I delete .git/refs/stash and repeat the process, I find the same results. 
The contents of .git/refs/stash are also embedded within
.git/logs/refs/stash, if that fact means anything.  Can Anyone point Me in
the direction of documentation on this particular problem to help clear up
why this is happening and which might help Me to determine what I should do
about it?

Thanks!

mi'e xuinkrbin.
-- 
View this message in context: http://old.nabble.com/While-the-awesome-switch-is-always-on%2C-so-is-the-confusion-switch.-tp28447763p28447763.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2010-05-04 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 15:17 xuinkrbin [this message]
2010-05-04 16:24 ` While the awesome switch is always on, so is the confusion switch Jonathan del Strother
2010-05-04 21:08   ` Jeff King

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=28447763.post@talk.nabble.com \
    --to=nabble.20.xuinkrbin@spamgourmet.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).