note common need of these two todos
This commit is contained in:
parent
d91b2b9fe2
commit
fccc9ab442
2 changed files with 9 additions and 0 deletions
|
@ -7,3 +7,7 @@ another 1.5x-2x speedup when such limits are used. What that optimisation
|
|||
needs is a way to tell if the current limit needs the key or not. If it
|
||||
does, then match on it after getting the key (and precaching the location
|
||||
log for limits that need that), otherwise before getting the key.
|
||||
|
||||
> So this needs a way to introspect a limit to see if the terms used in it
|
||||
> match some criteria. Another todo that also needs that is
|
||||
> [[sync_fast_import]] --[[Joey]]
|
||||
|
|
|
@ -32,3 +32,8 @@ So there would still be a conflict potential.
|
|||
May be worth removing support for matching annex.largefiles when the
|
||||
expression needs the file content, when importing from a special remote.
|
||||
Or could detect when those are used, and only import with --content then.
|
||||
|
||||
> So this needs a way to introspect a preferred content expression
|
||||
> to see if the terms used in it
|
||||
> match some criteria. Another todo that also needs that is
|
||||
> [[faster_key_lookup_for_limits]] --[[Joey]]
|
||||
|
|
Loading…
Reference in a new issue