summaryrefslogtreecommitdiff
path: root/doc/bugs/bare_git_repos.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-05-29 15:23:05 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-05-29 15:23:05 -0400
commit1f6cfecc972b121fa42ea80383183bbaccc2195a (patch)
tree0a450c4226f5e05c2a3597a9f520376de281fffe /doc/bugs/bare_git_repos.mdwn
parenta95fb731cd117f35a6e0fce90d9eb35d0941e26e (diff)
remove old closed bugs and todo items to speed up wiki updates and reduce size
Remove closed bugs and todos that were least edited before 2014. Command line used: for f in $(grep -l '\[\[done\]\]' *.mdwn); do if [ -z $(git log --since=2014 --pretty=oneline "$f") ]; then git rm $f; git rm -rf $(echo "$f" | sed 's/.mdwn$//'); fi; done
Diffstat (limited to 'doc/bugs/bare_git_repos.mdwn')
-rw-r--r--doc/bugs/bare_git_repos.mdwn29
1 files changed, 0 insertions, 29 deletions
diff --git a/doc/bugs/bare_git_repos.mdwn b/doc/bugs/bare_git_repos.mdwn
deleted file mode 100644
index 5e9100acf..000000000
--- a/doc/bugs/bare_git_repos.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-It would be nice if git-annex could be used in bare git repos.
-However, that is not currently supported. Problems include:
-
-* git-annex often does not read a git repo's config before touching it,
- so it doesn't know if the repo is bare or not
- (reading the config when operating on ssh repos would be a pain and SLOW;
- I had some of that code in as of 1aa19422ac8748eeff219ac4f46df166dae783c5,
- but ripped it all out)
-* .. which results in creating `.git/annex` in a bare repo, which mightily
- confuses git (so it will complain that the bare repo is not
- a git repo at all!)
-* `.git-annex/` needs to have state recorded to it and committed, and that
- is not possible with a bare repo. (If [[todo/branching]] were done,
- that might be fixed.) (now fixed)
-
-----
-
-Update: Now that git-annex-shell is used for accessing remote repos,
-it would be possible to add smarts about bare repos there, and avoid
-some of the above problems. Probably only the state recording problem
-remains.
-
-A possible other approach to the state recording repo is to not
-record state changes on the remote in that case. Git-annex already
-records remote state changes locally whenever it modifies the state of a
-remote. --[[Joey]]
-
-> And... [[done]]! See [[/bare_repositories]] for current status
-> and gotchas. --[[Joey]]