It doesn't seem to have hurt. But it doesn't seem to have helped either : now I have two problematic branches :
charpent@asus16-ec:/usr/local/sage-8$ git pull remote: Counting objects: 99, done. remote: Compressing objects: 100% (40/40), done. remote: Total 40 (delta 29), reused 0 (delta 0) Dépaquetage des objets: 100% (40/40), fait. Depuis git.sagemath.org:sage 3b454e23e9..eb6646e889 public/25097/qnormaliz-algebraic -> origin/public/25097/qnormaliz-algebraic error: cannot lock ref 'refs/remotes/origin/u/embray/python3/sage-rings-polynomial-polydict/misc': 'refs/remotes/origin/u/embray/python3/sage-rings-polynomial-polydict' existe ; impossible de créer 'refs/remotes/origin/u/embray/python3/sage-rings-polynomial-polydict/misc' ! [nouvelle branche] u/embray/python3/sage-rings-polynomial-polydict/misc -> origin/u/embray/python3/sage-rings-polynomial-polydict/misc (impossible de mettre à jour la référence locale) * [nouvelle branche] u/mkoeppe/experimental_flint_upgrade_package_tracking_trunk -> origin/u/mkoeppe/experimental_flint_upgrade_package_tracking_trunk Of course, I could manually rm .git/refs/remotes/origin/u/embray/python3/sage-rings-polynomial-polydict/ (which is empty), thus deleting the locale reference to this branch, but I absolutely ignore what other consequences this would have. Any suggestion ? Le samedi 22 septembre 2018 21:31:25 UTC+2, Dima Pasechnik a écrit : > > I don't see why `git gc` would hurt it. > > On Sat, 22 Sep 2018, 20:24 Emmanuel Charpentier, <emanuel.c...@gmail.com > <javascript:>> wrote: > >> 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> >>> 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. >>>> To post to this group, send email to sage-...@googlegroups.com. >>>> 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+...@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.
