On 12/05/2015 08:44 AM, Jeff King wrote: > [...] > I think the config option needs to be extensions.refsBackendType, too, > per the logic in 00a09d5 (introduce "extensions" form of > core.repositoryformatversion, 2015-06-23). And I guess it needs to bump > core.repositoryformatversion to "1".
I think also, strictly speaking, the extensions.refsBackendType option should be ignored if core.repositoryFormatVersion is not "1". In practice, it probably makes more sense for the code to error out in that case because it is likely the result of a bug. Note that if the user explicitly chooses the "files" backend, it would be preferable to leave "core.repositoryFormatVersion" at "0" (assuming that no other extension is being used) and leave "extensions.refsBackendType" unset. This approach creates a repository that is compatible with older clients that don't know about refsBackendTypes. Michael -- Michael Haggerty mhag...@alum.mit.edu -- 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
