From: "Simon Strandgaard" <neoneye@gmail.com>
To: git@vger.kernel.org
Subject: bug: git-stash save and symbolic links
Date: Mon, 20 Oct 2008 10:34:53 +0200 [thread overview]
Message-ID: <df1390cc0810200134x68a8eb1fyc7f24650c8c9c5d3@mail.gmail.com> (raw)
git-stash cannot find the repository when the path is a symbolic link.
solution for me was to cd to the absolute path and then do git-stash.
FAILURE: git-stash with symbolic link.
prompt> pwd
/Users/neoneye/st
prompt> ls -la ~/st
lrwxr-xr-x 1 neoneye neoneye 38 10 Okt 07:40 /Users/neoneye/st ->
/Users/neoneye/git/code/source_toolbox
prompt> git-stash
fatal: Not a git repository
fatal: Not a git repository
fatal: Not a git repository
You do not have the initial commit yet
prompt>
SUCCESS: git-stash without symbolic link.
prompt> pwd
/Users/neoneye/git/code
prompt> ls -la
drwxr-xr-x 16 neoneye neoneye 544 20 Okt 10:18 .git
drwxr-xr-x 29 neoneye neoneye 986 16 Okt 13:04 source_toolbox
prompt> git stash save "did I mess up"
Saved working directory and index state "On master: did I mess up"
HEAD is now at 90ac45d we can now seek through a WAV file.. finally.
prompt>
I think the problem is located in the save_stash() function, but
im not good at sh scripting to make a patch.
Thank you very much for git!
--
Simon Strandgaard
http://toolboxapp.com/
next reply other threads:[~2008-10-20 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 8:34 Simon Strandgaard [this message]
2008-10-20 15:17 ` bug: git-stash save and symbolic links Jeff King
2008-10-20 15:32 ` Simon Strandgaard
2008-10-20 15:39 ` Simon Strandgaard
2008-10-20 17:55 ` 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=df1390cc0810200134x68a8eb1fyc7f24650c8c9c5d3@mail.gmail.com \
--to=neoneye@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).