Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > > > This series teaches "jgit fetch" how to prune stale tracking branches > > that have been removed from the remote repository. We can now do > > both a fetch and a prune in a single network connection. > > I am not sure if that is a good feature. > > The user at the local side may well be using the (now stale) tracking > branch as an achoring point to remember where his own development forked > from, and that may be the reason he is fetching but not running "remote > prune", not to lose that anchor. Well. Its off by default. You have to ask for it with "jgit fetch --prune origin". Compare to asking for it with "git remote prune origin". We're already opening a #@!*@!* network connection to perform either fetch or prune, so we might as well let the user perform both in one step. Which is what this patch does. -- Shawn. -- 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
