Warn about unsupported core.sharedRepository=0xxx when set
This spams the user with a lot of messages, but it seems like busywork to avoid that and only warn once, since this warning will go away when it gets implemented. Also fix parsing of the octal value. Sponsored-by: Kevin Mueller on Patreon
This commit is contained in:
parent
4881bc5a53
commit
7af75a59be
4 changed files with 57 additions and 18 deletions
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 2"""
|
||||
date="2023-04-26T16:50:23Z"
|
||||
content="""
|
||||
I don't think it would be that hard to implement, I count 6 places, all in
|
||||
Annex.Perms that don't handle UmaskShared.
|
||||
|
||||
For now I've made all of them display a warning.
|
||||
|
||||
(Note that your warning patch to datalad is probably buggy,
|
||||
since core.sharedrepository=1 and =2 are supported by git-annex.
|
||||
(As legacy alternatives to "group" and "everybody".))
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue