Added a comment
This commit is contained in:
parent
25fb248277
commit
7ee30bd1ac
1 changed files with 18 additions and 0 deletions
|
@ -0,0 +1,18 @@
|
|||
[[!comment format=mdwn
|
||||
username="gernot"
|
||||
ip="213.168.117.192"
|
||||
subject="comment 2"
|
||||
date="2011-04-03T15:35:52Z"
|
||||
content="""
|
||||
'git add .git-annex' didn't do anything. That's when I noticed that this
|
||||
repository is on a case-insensitive HFS+ file system.
|
||||
|
||||
So, if I get this right it's not a new bug, but similar to this situation:
|
||||
[[git-annex_directory_hashing_problems_on_osx]]
|
||||
|
||||
Assuming that it was the file system's fault, I went ahead and upgraded yet
|
||||
another clone. That one (on an ext3 file system) had neither staged changes
|
||||
nor left-over untracked files. Everything seems to just have fallen right into
|
||||
place. Is that possible or still weird?
|
||||
|
||||
"""]]
|
Loading…
Reference in a new issue