mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2019-06-27 10:44:35 -04:00
parent 8add155f31
commit fb72f4db64
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
doc/todo/unlock_--read-only/comment_4_515e21cf5c2dfbf9fd780af9cef2e726._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-06-27T14:36:59Z"
content="""
It sounds like you would want to unlock all files in the repo this
way, is that right?
If so, it seems like a case for `git-annex adjust`, eg
`git annex adjust --hardlink`. And it would perhaps make sense to do
that on a crippled filesystem by default instead of the current default of
--unlock.
Keeping it in adjust only avoids needing to make the unlock command do
something that is not an unlocking, and it avoids needing to add a new
command.
It also neatly avoids the problem that, while `git annex unlock`
makes a change that can be committed to git (in v7 mode), this new
operation is not something that can be committed to git
(at least w/o some change to indicate it in the pointer file).
"""]]