Carlos Martín Nieto <cmn@xxxxxxxx> writes: > On Mon, 2011-09-26 at 15:30 -0700, Junio C Hamano wrote: >> Ben Boeckel <mathstuf@xxxxxxxxx> writes: >> >> > When the --prune and --tags options are given to git fetch together, all >> > non-tag refs are pruned because only tags are looked at and when pruning >> > it appears as if the branches have disappeared and are therefore deleted >> > locally. >> >> I would call that a bug, and it is not limited to the use of "--tags". For >> example, I suspect that >> >> $ git fetch --prune origin refs/heads/master:refs/remotes/origin/master >> >> would prune remote tracking branches for "origin" other than "master". > > This should fix it (in a way). Let's agree that it's a bad idea and > complain to the user. That might be a reasonable short-term safety measure, but in the longer term I think we should fix it properly. We are already learning "what are the refs the remote side currently has" from the transport and the right fix ought to be to use that original information, not the version filtered for the use of the primary objective of fetch, which is to only fetch what the user asked for. -- 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