Re: Avoiding broken Gitweb links and deleted objects

From: William Swanson <swansontec@gmail.com>
Date: May 22, 2013, 15:41 UTC
Message-ID: <CABjHNoQEpjE8Da2qiU8o5LRWs7CrUW44XcV7T=tcnB_Z1z+Uvg@mail.gmail.com>
In-Reply-To: <CAJELnLEGr7eG9W2WvcVjWi7rT6EUhBDVdtfx6Xjp15duB0E9kw@mail.gmail.com>

On Wed, May 22, 2013 at 6:32 AM, Matt McClure <matthewlmcclure@gmail.com> wrote:

> Is there a way to push/pull reflogs among different repositories?

Not that I am aware of, at least not in core git.

Show 11 quoted lines

> In my original scenario:
>
> 1. the commits are created on a developer machine
> 2. pushed to a central origin repository running Gitweb
> 3. the branch is rebased on the developer machine
> 4. the branch is push --force'd to the origin
>
> Later, git push tells me:
>
>     warning: There are too many unreachable loose objects; run 'git
> prune' to remove them.

You don't need to share reflogs in this case. Assuming the server were to keep logs of its own, the forced update would create a new reflog entry showing something like "<old-sha> <new-shaw> <date info> Forced push", so the pre-rebase version would still be reachable from the reflogs, keeping it around.

> or I want to delete old topic branch HEADs to improve performance.
>
> But I never want to let Git delete the underlying commit objects since
> there could be Gitweb links pointing at them.

The reflog thing won't help you in this case, since reflogs are deleted when their branches are deleted. it sounds like you never want to delete anything, so it would make more sense to just disable garbage collection entirely.

-William