> Yeah after thinking more about this I wonder if we have some mental model that we want to teach to the users? What is the fetch command (using the ref-in-want capability) supposed to do? * update to the latest state observed by the latest remote talked to? * update to some approximate state that is converged from multiple remotes? * update to a state that the first remote had, that we talked to
Having such a model would make it easier for me to follow this discussion. > I agree, we should have the client > fail out and require that the server MUST not send additional refs. This is reasoned for by the way we evolve the client, not some state the user expects to see short or longterm? > This can of course be loosened through a capability if we want to do > something else in the future. Thanks for sanity checking me :) ok, that is a sensible way to go forward.
