Junio C Hamano <gitster@xxxxxxxxx> writes: > Nicolas Pitre <nico@xxxxxxx> writes: > >>> This patch does not add invocation of the "auto repacking". It >>> is left to key Porcelain commands that could produce tons of >>> loose objects to add a call to "git gc --auto" after they are >>> done their work. Obvious candidates are: >>> >>> git add >> >> Nope! 'git add' creates loose objects which are not yet reachable from >> anywhere. They won't get repacked until a commit is made. > > Bzzt, I am releaved to see you are sometimes wrong ;-) > > They are reachable from the index and are not subject to > pruning. Hm. Isn't it possible to work with several index files at once? I seem to remember that even git-add does this itself. So what is it that protects objects in such a temporary index from being garbage collected by a different git process running on the same repository? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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
