- User Since
- Jun 29 2017, 2:56 PM (197 w, 4 d)
Sun, Apr 11
Fri, Apr 9
What if we use a different file ? This would allow us to use a different semantic an adjusted plan for a smoother transition.
(I am stopping my review here since I am the actual author of those)
(maybe explain why in your description, the behavior is already "encoded" in the patch)
Do you have any performance number for that update ? for example the time we need to do that full some known large repositories, and the impact on a clone ?
Thu, Apr 8
This is all true.
+1 (the set binding was not available at the time of writing, but they are not need to keep doing this now.)
What happens in the stream clone case ? Or during the transition from older to newer client ? streaming content from an older clone will not contains a fully up to date cache, and existing repository neither. How are we dealing with this ?