Jeff King <peff@xxxxxxxx> writes: > It _could_ still be useful in a more isolated environment (e.g., your > company server that is serving only internal repos to employees). But I > have misgivings about a feature that lets people intentionally create > repositories whose history cannot ever interact with other users who > haven't set a special config flag. It's one thing to say "to take > advantage of this feature, we must all agree to have version X, or set > flag Y". But it's another to bake that restriction into the repository > history for all time. If people want a pre-prepared repository propagated to CI environment and keep trakc of the state of such repository over time, for example, they can use (versioned) tarballs. Such a tarball won't automatically get extracted after "git pull" (which is a feature), but those who want such a pre-prepared repository for CI can make the extraction step as a part of their CI build procedure.
