Shawn O. Pearce <spearce <at> spearce.org> writes: > > Sergio <sergio.callegari <at> gmail.com> wrote: > > Version 1.5.6.5 > > > > Looks weird > > Is it the intended behaviour? > > This is the current (intended) behavior. We have never pruned an > object from a repository unless the object is packed in the shared > alternate repository. See git-prune-packed's man page. The prune > logic for loose objects only deletes objects which are in packs, > and it doesn't care where that pack came from. > Many thanks for the explanation. Two more questions: 1) Is there a way to prune objects that are anyway available at the alternate without touching the alternate (to repack it)? 2) Would there be any contraindication in doing so? (namely, is the current behaviour of git gc a mere consequence of the prune-packed logic or a behaviour purposely introduced for safety?) Sergio -- 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
