diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9FMhhhM2sJ68Zjx_RmWd8cTdpI-mrkbE <Hans@web> | 2013-06-04 08:00:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-06-04 08:00:15 +0000 |
| commit | 21df5d9e8eae089ad22dac1851461bbee3331d01 (patch) | |
| tree | 17ca7116c7db8d338bc5de0b399b709ba05f1a90 | |
| parent | be8c2cdf872a8327a78225de18462c1115472297 (diff) | |
Added a comment: what about with git-svn?
| -rw-r--r-- | doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_2_b5e94c10ebbed9125c7e2332f75709ca._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_2_b5e94c10ebbed9125c7e2332f75709ca._comment b/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_2_b5e94c10ebbed9125c7e2332f75709ca._comment new file mode 100644 index 000000000..ba321df6b --- /dev/null +++ b/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_2_b5e94c10ebbed9125c7e2332f75709ca._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl9FMhhhM2sJ68Zjx_RmWd8cTdpI-mrkbE" + nickname="Hans" + subject="what about with git-svn?" + date="2013-06-04T08:00:15Z" + content=""" +I'm trying to wrap my head around a similar situation. +I've tested this by git cloning my repo; the symlinks are copied, and end up broken because the annex directory under .git doesn't exist in the new repo. + +So to be specific: can I conclude that when I use git to copy my repo, as long as I don't explicitly use git-annex in the process, I end up with a 'bare' git repo and I don't have to worry about my annexed files coming along? + +Also: anyone know of anything that would be different about using git-svn? (i.e. git svn dcommit to push my changes to an svn repo)? +"""]] |