On Wed, May 8, 2013 at 12:05 PM, Matt McClure <matthewlmccl...@gmail.com> wrote: > On Wed, May 8, 2013 at 10:41 AM, Johannes Sixt <j.s...@viscovery.net> wrote: >> git gc moves unreachable objects that were packed before to the loose >> object store, from where they can be pruned. > > Thanks. That was the piece I was missing. I assumed `git gc` did the opposite.
That begs a follow-up question. It sounds as though Git will typically delete unreachable objects. My team often shares links like https://git.example.com/foo.git/log/d59051721bb0a3758f7c6ea0452bac122a377645?hp=0055e0959cd13780494fe33832bae9bcf91e4a90 . If I later rebase the branch containing those commits and d590517 becomes unreachable, do I risk that link breaking when Git deletes d590517? What's a good strategy for avoiding breaking those links? -- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
