mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

removed

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawl9FMhhhM2sJ68Zjx_RmWd8cTdpI-mrkbE 2013-06-04 07:56:45 +00:00 committed by admin
parent 621a110246
commit 780682cda1
1 changed files with 0 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/forum/using_git_and_git-annex_side_by_side:_with_git-svn.mdwn
View file

@ -1,11 +0,0 @@
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