Jeff King <p...@peff.net> writes: > Yes, we don't let normal fetchers see these repos. They're only for > holding shared objects and the ref tips to keep them reachable.
Are these individual refs have relations to the real world after they are created? To ask it another way, let's say that a branch in a repository, which is using this as a shared object store, caused one of these refs to be created; now the origin repository rewinds or deletes that branch---do you do anything to the ref in the shared object store at that point? I am wondering if it makes sense to maintain a single ref that reaches all the commits in this shared object store repository, instead of keeping these millions of refs. When you need to make more objects kept and reachable, create an octopus with the current tip and tips of all these refs that causes you to wish making these "more objects kept and reachable". Obviously that won't work well if the reason why your current scheme uses refs is because you adjust individual refs to prune some objects---hence the first question in this message. -- 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
