Okay. But this means I have to wait for this pruning... Unless you tell me it's a bad idea (and why), I'll try to git gc --agressive. At worst, Ill have to retry from a fresh clone...
Le samedi 22 septembre 2018 21:19:59 UTC+2, Dima Pasechnik a écrit : > > IMHO it's the main tree that might use some pruning, as we now see the > second case of it being uncooperative.... > > On Sat, 22 Sep 2018, 19:55 Emmanuel Charpentier, <emanuel.c...@gmail.com > <javascript:>> wrote: > >> Should I try git gc (or possibly git gc aggressive) ? >> Wouldn't this make my tree potentially unfit to future pushes ? >> >> Le samedi 22 septembre 2018 20:27:08 UTC+2, Emmanuel Charpentier a écrit : >> >> [ Snip... ] >> >> -- >> 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+...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
