On Fri, May 10, 2013 at 3:34 AM, William Swanson <swansontec@xxxxxxxxx> wrote:
> I started working on something like this a few weeks ago, but
> eventually came to the conclusion that this information does not
> belong in the commit graph itself.
>
> A better approach, I think, would be to enhance the reflogs to the
> point where they can provide this information in a reliable manner.
Is there a way to push/pull reflogs among different repositories?
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.
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.
--
Matt McClure
http://matthewlmcclure.com
http://www.mapmyfitness.com/profile/matthewlmcclure
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html