deal with ignoreinode config setting
Improve handling of directory special remotes with importtree=yes whose
ignoreinode setting has been changed. (By either enableremote or by
upgrading to commit 3e2f1f73cb
.)
When getting a file from such a remote, accept the content that would have
been accepted with the previous ignoreinode setting.
After a change to ignoreinode, importing a tree from the remote will
re-import and generate new content identifiers using the new config. So
when ignoreinode has changed to no, the inodes will be learned, and after
that point, a change in an inode will be detected as a change. Before
re-importing, a change in an inode will be ignored, as it was before the
ignoreinode change. This seems acceptble, because the user can re-import
immediately if they urgently need to add inodes. And if not, they'll
do it sometime, presumably, and the change will take effect then.
Sponsored-by: Erik Bjäreholt on Patreon
This commit is contained in:
parent
4a1030d51d
commit
1fe9cf7043
4 changed files with 34 additions and 2 deletions
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2022-09-16T17:43:38Z"
|
||||
content="""
|
||||
I've made the directory special remote treat content identifiers
|
||||
that differ only in one having the inode set to 0. Which will avoid it
|
||||
failing in the situation I showed.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue