diff options
| author |  gernot <gernot@web> | 2011-04-03 15:35:53 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-04-03 15:35:53 +0000 |
| commit | 7ee30bd1ac68c47c009c703ce967f1362af96302 (patch) | |
| tree | 384ab378fd8ae052d79b197a1271bc536c941222 /doc/bugs | |
| parent | 25fb248277a7d970e301806d2bcbec71e987b20b (diff) | |
Added a comment
Diffstat (limited to 'doc/bugs')
| -rw-r--r-- | doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment new file mode 100644 index 000000000..4fc9647e8 --- /dev/null +++ b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment @@ -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? + +"""]] |