From: Alexey Muranov <alexey.muranov@gmail.com>
Date: Thu, 19 Jul 2012 16:51:15 GMT
Subject: Re: Feature request: fetch --prune by default
Message-ID: <733EACD1-353C-4256-BA8B-DFDCE1C7D6F1@gmail.com>
In-Reply-To: <CAPBPrntB3ixuRFDP5fp8saJoEZvYOEd631Nh2=-WGudB-UK=kw@mail.gmail.com>

On 19 Jul 2012, at 18:48, Dan Johnson wrote:

> From the git-gc man page:
> git gc tries very hard to be safe about the garbage it collects. In
> particular, it will keep not only objects referenced by your current
> set of branches and tags, but also objects referenced by the index,
> remote-tracking branches, refs saved by git filter-branch in
> refs/original/, or reflogs (which may reference commits in branches
> that were later amended or rewound).
> 
> So yes, a reflog entry does stop gc from removing objects, including
> commits. It will expire old reflog entries (90 days by default)
> though, so it's not like they will stay around forever.

Dan, thanks for the explanation.

Alexey.