Pruning is about unreachable objects (commits not referenced by a branch, e.g. because you deleted the branch). It is safe to do unless you accidentally deleted a branch and want it back ;-)
A better command to clean up temporary files is "git gc" which includes pruning On Tuesday, April 5, 2016 at 9:24:52 AM UTC+2, Emmanuel Charpentier wrote: > > Pushing to Trac#20190 <http://trac.sagemath.org/ticket/20190> , I got : > > charpent@asus16-ec:/usr/local/sage-exp$ git trac push > Pushing to Trac #20190... > Guessed remote branch: u/charpent/upgrade_r_to_3_2_4 > > remote: Trac #20190: Commit changed to feb037. > Auto packing the repository for optimum performance. > warning: There are too many unreachable loose objects; run 'git prune' to > remove them. > To g...@trac.sagemath.org:sage.git > 385c51d..feb037a HEAD -> u/charpent/upgrade_r_to_3_2_4 > > 1) What does that mean ? > > 2) Is "pruning" compatible with Sage's *modus operandi* ? > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
