On Mon, May 14, 2012 at 10:18 PM, Sverre Rabbelier <srabbelier@xxxxxxxxx> wrote: > On Mon, May 14, 2012 at 4:09 AM, Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> wrote: >> I'm good with always warning too. The moment it shows up, I can just >> open another terminal for "gc". Though (I guess) a new user in the >> middle of the work may not want to do that as they fear "gc" may >> interfere their work. > > If we know that it won't interfere with their work, can we just spawn > git gc as a background process? I thought of that for index-pack, but we would need to deal with error messages from gc messing up with foreground command's. I don't like a command leaving background processes (without asking me) after it exits, so index-pack should hang on until gc finishes. Which is ok for long time commands like index-pack, but not ok for commit, rebase... -- Duy -- 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