Re: [JGIT PATCH 0/6] Add prune of stale tracking branches to fetch

From: Shawn O. Pearce <spearce@spearce.org>
Date: Feb 13, 2009, 00:42 UTC
Message-ID: <20090213004245.GZ30949@spearce.org>
In-Reply-To: <7v7i3vi33b.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> "Shawn O. Pearce" <spearce@spearce.org> 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.