Re: [RFC] Add --create-cache to repack

[Johannes Sixt <j.sixt@viscovery.net>]

Am 1/28/2011 9:06, schrieb Shawn O. Pearce:
> A cache pack is all objects reachable from a single commit that is
> part of the project's stable history and won't disappear, and is
> accessible to all readers of the repository.  By containing only that
> commit and its contents, if the commit is reached from a reference we
> know immediately that the entire pack is also reachable.  To help
> ensure this is true, the --create-cache flag looks for a commit along
> refs/heads and refs/tags that is at least 1 month old, working under
> the assumption that a commit this old won't be rebased or pruned.

In one of my repositories, I have two stable branches and a good score of
topic branches of various ages (a few hours up to two years 8). The topic
branches will either be dropped eventually, or rebased.

What are the odds that this choice of a tip commit picks one that is in a
topic branch? Or is there no point in using --create-cache in a repository
like this?

-- Hannes