From: Alexey Muranov <alexey.muranov@gmail.com>
Date: Thu, 19 Jul 2012 16:40:48 GMT
Subject: Re: Feature request: fetch --prune by default
Message-ID: <CA80E335-AD87-4DFC-9569-A010D3E850C0@gmail.com>
In-Reply-To: <20120719115558.GC29774@sigill.intra.peff.net>

On 19 Jul 2012, at 13:55, Jeff King wrote:

> I agree it would be much less confusing. However, one downside is that
> we do not keep reflogs on deleted branches (and nor did the commits in
> remote branches necessarily make it into the HEAD reflog). That makes
> "git fetch" a potentially destructive operation (you irrevocably lose
> the notion of which remote branches pointed where before the fetch, and
> you open up new commits to immediate pruning by "gc --auto".

If i understand correctly, existence of a reflog entry will not stop "gc" from removing a commit, will it?
In this case, if a remote branch was rebased or reset, commits can be lost anyway, right?

Alexey.