From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 05 Mar 2013 18:15:20 GMT
Subject: Re: [PATCH 2/2] push: --follow-tag
Message-ID: <7vobexu30n.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20130305172233.GA9379@sigill.intra.peff.net>

Jeff King <peff@peff.net> 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.