From 57a0ef8d90e0bf4c7a95747efb41d88d80888be3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 27 May 2021 12:19:35 -0400 Subject: [PATCH] comment and reject todo --- ...directory_special_remote_in_bare_repo.mdwn | 2 ++ ..._01e0c35f74a81ae06d0f93a6b00e003c._comment | 22 +++++++++++++++++++ 2 files changed, 24 insertions(+) create mode 100644 doc/todo/customisable_directory_special_remote_in_bare_repo/comment_3_01e0c35f74a81ae06d0f93a6b00e003c._comment diff --git a/doc/todo/customisable_directory_special_remote_in_bare_repo.mdwn b/doc/todo/customisable_directory_special_remote_in_bare_repo.mdwn index a57609bfa2..4c6b843c99 100644 --- a/doc/todo/customisable_directory_special_remote_in_bare_repo.mdwn +++ b/doc/todo/customisable_directory_special_remote_in_bare_repo.mdwn @@ -3,3 +3,5 @@ AFAICT, the `annex/` subdir in a bare annex repo is the exact same layout as a d It'd be very useful if its parameters could be customised just like an actual directory special remote to allow for e.g. encrypted and/or chunked storage. I have a use-case where this could significantly simplify things. An interesting side-effect of this would be a tweakable location for a bare repo's storage which could be used to separate metadata and data (i.e. git repo on SSD for fast syncs and actual data on an HDD). + +> [[rejected|done]] --[[Joey]] diff --git a/doc/todo/customisable_directory_special_remote_in_bare_repo/comment_3_01e0c35f74a81ae06d0f93a6b00e003c._comment b/doc/todo/customisable_directory_special_remote_in_bare_repo/comment_3_01e0c35f74a81ae06d0f93a6b00e003c._comment new file mode 100644 index 0000000000..c6c5dce02f --- /dev/null +++ b/doc/todo/customisable_directory_special_remote_in_bare_repo/comment_3_01e0c35f74a81ae06d0f93a6b00e003c._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-05-27T16:15:31Z" + content=""" +It would not make sense for a non-bare git repository to have annexed +contents in it encrypted or chunked, because that would prevent actually +accessing the annexed files at all; git-annex symlinks have to point to a +complete, non-encrypted file. + +Bare git repositories are a very minor special case of non-bare git +repositories; they do not have a work tree or index. In other +respected, they are the same, and it's entirely possible to manually +convert a git repo to or from bare, or even temporarily use a bare repo +with a work tree. + +It would be extremely inelegant if git-annex did something that broke +that. Which this would. + +I think you should use a rsync special remote possibly. Which also has the +same layout as a directory special remote. +"""]] -- 2.30.2