From 621a1102464598bc0a3d747a9723ab2c2e57d5c5 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9FMhhhM2sJ68Zjx_RmWd8cTdpI-mrkbE" Date: Tue, 4 Jun 2013 07:55:40 +0000 Subject: [PATCH] question about git and git-annex side by side, also with git-svn --- ..._git_and_git-annex_side_by_side:_with_git-svn.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/using_git_and_git-annex_side_by_side:_with_git-svn.mdwn diff --git a/doc/forum/using_git_and_git-annex_side_by_side:_with_git-svn.mdwn b/doc/forum/using_git_and_git-annex_side_by_side:_with_git-svn.mdwn new file mode 100644 index 0000000000..d45fa0749e --- /dev/null +++ b/doc/forum/using_git_and_git-annex_side_by_side:_with_git-svn.mdwn @@ -0,0 +1,11 @@ +This question happens to have overlap with the recent http://git-annex.branchable.com/forum/help_running_git-annex_on_top_of_existing_repo/ + +I have a git repository which I want to keep in sync with an svn repository via git-svn. My git repository with annex stores large files (database dumps) in annex. I'm having trouble understanding how git-annex will hand off to git, and to git-svn. If I want to merge my repo to another git repo, or on to svn, do I have to do anything special to make sure my large files are not copied? + +I tested this by cloning the git repo. The symlinks are copied, and become broken as they obviously point to the annex directory which is not copied by the clone. + +The lesson seems to be: if you git clone or merge to a repo that is NOT annex enabled, you will end up with a normal git repo without any annex stuff. So as long as I don't explictly use git-annex, I can safely copy my other files to other repositories, and not worry about my annexed files coming along. Is this a safe conclusion for me to work with? Also, does anyone know of anything specific that would be different using git svn dcommit to merge my changes to an svn repo? + +Thanks. + +Hans