fixed in v10

diff --git a/doc/bugs/Wrong_permission_when_using_shared_repository.mdwn b/doc/bugs/Wrong_permission_when_using_shared_repository.mdwn
index 8f135149a4c5c097e360ad01a8a5c6115b11fa41..bcb217dd01cc6ab96392fa1cced8a192a6ecc15d 100644 (file)
--- a/doc/bugs/Wrong_permission_when_using_shared_repository.mdwn
+++ b/doc/bugs/Wrong_permission_when_using_shared_repository.mdwn
@@ -64,3 +64,5 @@ My motivation here is the following: I want to use the git-annex as an (external
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 I have used git-annex in a single-user scenario yet. So far it works like a charm. I need more time to learn to get a hold of all functions but this is okay.
+
+> [[done]] in v10 --[[Joey]]

diff --git a/doc/bugs/Wrong_permission_when_using_shared_repository/comment_1_bfcb858bfd1c5377c2b15961b59a835a._comment b/doc/bugs/Wrong_permission_when_using_shared_repository/comment_1_bfcb858bfd1c5377c2b15961b59a835a._comment
new file mode 100644 (file)
index 0000000..8050f68
--- /dev/null
+++ b/doc/bugs/Wrong_permission_when_using_shared_repository/comment_1_bfcb858bfd1c5377c2b15961b59a835a._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-08-17T16:38:40Z"
+ content="""
+This was necessary to allow locking the object files.
+
+Repository v10 fixed that, so if you upgrade your repository, 
+you will no longer have this problem. Run `git-annex upgrade`.
+"""]]