On Tue, Mar 11, 2014 at 8:49 AM, Jeff King <p...@peff.net> wrote: > Right, I recall the general feeling being that such a system would work, > and the transition would be managed by a config variable like > "remote.*.useUploadPack2". Probably with settings like: > > true: > always try, but allow fall back to upload-pack > > false: > never try, always use upload-pack > > auto: > try, but if we fail, set remote.*.uploadPackTimestamp, and do not > try again for N days > > The default would start at false, and people who know their server is > very up-to-date can turn it on. And then when many server > implementations support it, flip the default to auto. And either leave > it there forever, or eventually just set it to "true" and drop "auto" > entirely as a code cleanup.
I would add that upload-pack also advertises about the availability of upload-pack2 and the client may set the remote.*.useUploadPack2 to either yes or auto so next time upload-pack2 will be used. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
