Jeff King <peff@xxxxxxxx> writes: > The current protocol relies on certain repository properties on the > remote end that narrow clone will violate. I don't see a way around that > without a protocol extension to communicate the narrowness. What will > that extension look like? It would have to involve exchanging "I have/am interested in the paths that match these pathspecs". I do not mind if our initial implementation did not support anything other than fetching into a narrow from full and pushing from a narrow to full. The second iteration could add fetching and pushing between two narrows with the same set of narrowing pathspecs. As to widening the area after a clone is made, I do not mind and if our initial impementation only supported widening the area in a stupid way (e.g. semi-equivalent of initial clone with the widened set of narrowing pathspecs). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html