Thread (1 message) 1 message, 1 author, 2018-01-30

Re: [PATCH v2 1/1] setup: recognise extensions.objectFormat

From: Junio C Hamano <hidden>
Date: 2018-01-30 20:53:56

Jeff King [off-list ref] writes:
Putting code in master is OK; we can always refactor it. But once we
add and document a user-facing config option like this, we have to
support it forever. So that's really the step I was wondering about: are
we sure this is what the user-facing config is going to look like?
Yup, that is an important distinction.
But that's sort of my point. It appears to be working, but the
prior-version safety they think they have is not there. I think we're
better off erring on the side of caution here, and letting them know
forcefully that their config is bogus.
quoted
At the same time... there's extension.partialclone in pu and it does not
have check on repo format.
IMHO it should (and we should just do it by enforcing it for all
extensions automatically).
Sounds good.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help