diff options
author | 2016-01-28 19:03:08 +0000 | |
---|---|---|
committer | 2016-01-28 19:03:08 +0000 | |
commit | eca4e691b43e0b84c866f4cf5d56875367d496f1 (patch) | |
tree | f4bd548ab6999e2a10e307105d5cfdd781a5d3da | |
parent | 0539e31a498539a7b7ca7f21764f595113ea9b1f (diff) |
Added a comment: Does a tar of `.git` solve the problem
-rw-r--r-- | doc/forum/Repository_backup/comment_3_ead30baf0a6d718569feb4002ba19b9e._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Repository_backup/comment_3_ead30baf0a6d718569feb4002ba19b9e._comment b/doc/forum/Repository_backup/comment_3_ead30baf0a6d718569feb4002ba19b9e._comment new file mode 100644 index 000000000..3db7f7d18 --- /dev/null +++ b/doc/forum/Repository_backup/comment_3_ead30baf0a6d718569feb4002ba19b9e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="git-annex.branchable.com@69b3f2da2837a3d9de8eab0b93771008294b7d69" + nickname="git-annex.branchable.com" + subject="Does a tar of `.git` solve the problem" + date="2016-01-28T19:03:08Z" + content=""" +Just wondering if tarring .git (excluding .git/annex of course}) into a file in the root of the repo will serve this purpose? Seems like it would to me... How would one restore from this... it'd be (practically) a bare repo right? +"""]] |