summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus <Jimmy@web>2011-03-27 16:53:51 +0000
committerGravatar admin <admin@branchable.com>2011-03-27 16:53:51 +0000
commitbb7688233bd10773ab75eba7135497ae10af9061 (patch)
treeba0803065d88450c1fc20c5462abf21659da6f32
parent5daf33d557291f1467a995f6c26f193e9323dd95 (diff)
-rw-r--r--doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn b/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
index d1a3c0607..2315bbb83 100644
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
+++ b/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
@@ -26,6 +26,8 @@ this has somewhat confused git when it tries to stage/merge files, I didn't noti
> .git-annex manually?) I don't understand how you get to this state.
> --[[Joey]]
+>> I think I got myself into this situation when I copied some files over from a HFS+ partition to a GPFS network share (which is pretty posix compliant) over samba. It probably is related to the [[git-annex_has_issues_with_git_when_staging__47__commiting_logs]]. I thought they were unique enough to have two bug reports logged as one is a git behavioural thing and the other is git-annex specific.
+
Also I came across this when I accidentally annexed some files in the .git-annex directory and it cause git-annex/git to be very unhappy when i pulled the repo to somewhere else. It might be worth teaching git-annex to disallow annex'ing of files inside the .git-annex/.git directories.
> There is a guard against `git annex add .git-annex/foo`, but it doesn't