Duy Nguyen <pclouds <at> gmail.com> writes: > On Fri, Feb 7, 2014 at 7:36 PM, chris <jugg <at> hotmail.com> wrote: > > Junio C Hamano <gitster <at> pobox.com> writes: > >> Instead of adding a boolean --break-ok that is hidden, why not > >> adding an exposed boolean --daemonize, and let auto-gc run in the > >> background? With the recent "do not let more than one gc run at the > >> same time", that should give a lot more pleasant end user > >> experience, no? > > > > That sounds quite useful to me. Duy, are you up for generating such a patch? > > It would not be so hard for that patch. I'm still thinking whether it > should be done if auto-gc is started on the client side too (sometimes > it does, which is equally annoying).. That could be nice, but I'd be less concerned about that, as the client has the ability to disable gc for itself. Still pushing it into the background, if considered acceptable behavior, seems reasonable. Perhaps two separate patches? Chris -- 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