open todo
This commit is contained in:
parent
c2a44eab50
commit
b117f9338d
2 changed files with 22 additions and 0 deletions
|
@ -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.
|
||||||
|
"""]]
|
13
doc/todo/v9_changes.mdwn
Normal file
13
doc/todo/v9_changes.mdwn
Normal file
|
@ -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 <https://git-annex.branchable.com/bugs/shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/>
|
||||||
|
|
||||||
|
Note that windows already uses a separate lock file.
|
Loading…
Add table
Add a link
Reference in a new issue