diff options
author | Phyks <Phyks@web> | 2015-01-18 23:54:43 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2015-01-18 23:54:43 +0000 |
commit | 69b13d9583f9aff85308fd36fd087637676ab844 (patch) | |
tree | aaddc09f9eb1cd7a029f621d6575c6ed5f1d01b2 /doc | |
parent | eaa4ee9574879c8294ce1d0cefd13935a9a7d8d9 (diff) |
Diffstat (limited to 'doc')
-rw-r--r-- | doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn b/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn new file mode 100644 index 000000000..f28b3514e --- /dev/null +++ b/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn @@ -0,0 +1,15 @@ +### Please describe the problem. +When using git-annex in indirect mode (or even in direct mode I think, although this is not to be very reliable in this context), git repos inside a git-annex are ignored. This is due to the fact that git is ignoring nested .git folders, and then, we can safely work with git-annex and nested git repos without conflicts. + +Using a tool such as my-repos, one can then sync its entire home directory, containing folders and git repos, syncing the normal folders thanks to git-annex, and storing the git repos metadata for easy cloning using my-repos. + +However, when using the git-annex assistant (or the daemon to have automatic background sync), this is no longer the case. + +After discussion on IRC, we thought this could be due to the fact that files are copied sequentially and that the .git folder is not yet present when it starts copying. However, disabling the daemon, copying the files and reenabling it then leads to the same behaviour. + +Thanks! + + +### What version of git-annex are you using? On what operating system? + +git-annex-bin on AUR. |