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.


To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to