Jeff King <peff@xxxxxxxx> writes: > But I wonder if fetching and pushing are different in that respect. You > are (usually) fetching from a public publishing point, and it is assumed > that whatever is there is useful for sharing. The only reason to limit > it is to save time transferring objects the user does not want. There are those who have to emulate "git fetch" with a reverse "git push" (or vice versa) due to network connection limitations, so I do not think hardcoding such a policy decision in the direction is necessarily a good idea. > ... But I also don't want to introduce a feature > that causes people to accidentally publish cruft. It may not be a > problem in practice; I'm just thinking out loud at this point. Likewise. -- 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