wip
This commit is contained in:
parent
56478e99ac
commit
b470673e50
1 changed files with 5 additions and 8 deletions
|
@ -2,15 +2,12 @@ If the journal contains a newer version of a log file than the git-annex
|
||||||
branch, and annex.alwayscommit=false so the branch is not getting updated,
|
branch, and annex.alwayscommit=false so the branch is not getting updated,
|
||||||
the value from the journal can be ignored when reading that log file.
|
the value from the journal can be ignored when reading that log file.
|
||||||
|
|
||||||
In CmdLine.Seek, there is some code that precached location logs as an
|
In CmdLine.Seek, there is some code that precaches location logs as an
|
||||||
optimisation. That streams info from the git-annex branch into the cache.
|
optimisation (when using eg --copies). That streams info from the
|
||||||
But it never checks for a journal file.
|
git-annex branch into the cache. But it never checks for a journal file
|
||||||
|
with newer information.
|
||||||
|
|
||||||
One fix would be to just check the journal file too, but that would
|
> fixed this
|
||||||
probably slow down the optimisation and would not speed up anything. So I
|
|
||||||
think that the caching needs to note that it's got cached a value from the
|
|
||||||
git-annex branch, but that the journal file needs to be checked for before
|
|
||||||
using that cached data.
|
|
||||||
|
|
||||||
Also in Cmdline.Seek, there is a LsTreeRecursive over the branch to handle
|
Also in Cmdline.Seek, there is a LsTreeRecursive over the branch to handle
|
||||||
`--all`, and I think again that would mean it doesn't notice location
|
`--all`, and I think again that would mean it doesn't notice location
|
||||||
|
|
Loading…
Reference in a new issue