From 6a20fe275f6f2e8626480d7b0d4a4f9924c85207 Mon Sep 17 00:00:00 2001 From: "https://id.koumbit.net/anarcat" Date: Tue, 19 May 2015 12:18:06 +0000 Subject: Added a comment --- ...ent_5_6328134497c0de6a088087fc9cb0e59e._comment | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 doc/bare_repositories/comment_5_6328134497c0de6a088087fc9cb0e59e._comment (limited to 'doc') diff --git a/doc/bare_repositories/comment_5_6328134497c0de6a088087fc9cb0e59e._comment b/doc/bare_repositories/comment_5_6328134497c0de6a088087fc9cb0e59e._comment new file mode 100644 index 000000000..80906857e --- /dev/null +++ b/doc/bare_repositories/comment_5_6328134497c0de6a088087fc9cb0e59e._comment @@ -0,0 +1,31 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + subject="comment 5" + date="2015-05-19T12:18:05Z" + content=""" +Well, no, i don't think they changed, unless i missed something: there +shouldn't be a `.git` repository there. + +There are [various +instructions](http://stackoverflow.com/questions/10637378/how-do-i-convert-a-bare-git-repository-into-a-normal-one-in-place) +on how to do this online. They do seem to agree with the first comment +above. + +Personnally, I would just `git clone` to a different repo and `git +annex forget` the old one. Unless you have a very complex repository +with a lot of files, this is simple enough... You could even use `git +annex reinit` to recycle the previous uuid if that's a concern. So in +short: + + git clone repo.git repo + cd repo + git annex info --fast # find the UUID of repo.git + git annex move --from $UUID + git annex reinit $UUID + +Then `repo.git` can be removed if you are certain everything is +correct in `repo`. + +Note that you may want to have backups of everything before you do +anything, as usual. +"""]] -- cgit v1.2.3