From b117f9338df73ea12a6c1e702c5c473dc8b641f5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 12 Oct 2021 13:42:08 -0400 Subject: [PATCH] open todo --- ...ment_7_a82064795fdbdb0187763aeee4a308ff._comment | 9 +++++++++ doc/todo/v9_changes.mdwn | 13 +++++++++++++ 2 files changed, 22 insertions(+) create mode 100644 doc/bugs/shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_7_a82064795fdbdb0187763aeee4a308ff._comment create mode 100644 doc/todo/v9_changes.mdwn diff --git a/doc/bugs/shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_7_a82064795fdbdb0187763aeee4a308ff._comment b/doc/bugs/shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_7_a82064795fdbdb0187763aeee4a308ff._comment new file mode 100644 index 0000000000..add0385dd2 --- /dev/null +++ b/doc/bugs/shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_7_a82064795fdbdb0187763aeee4a308ff._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2021-10-12T17:40:51Z" + content=""" +I've opened [[todo/v9_changes]] and this can be taken care of if/when a v9 +happens. It's unfortunate I didn't think of this bug when doing v8, so +hopefully that new todo will remind me about it for v9. +"""]] diff --git a/doc/todo/v9_changes.mdwn b/doc/todo/v9_changes.mdwn new file mode 100644 index 0000000000..75b5648bcc --- /dev/null +++ b/doc/todo/v9_changes.mdwn @@ -0,0 +1,13 @@ +This is a todo for collecting changes that could lead to a v9 repository +version. + +Currently, there does not seem to be enough reason to warrant one, but that +could change and if it does, these things could be included. + +* Change locking of annexed files to use a separate lock file + rather than posix locking the file itself. + + This would let write bits be removed from the file when + core.sharedRepository is set. See + + Note that windows already uses a separate lock file.