Re: [PATCH] Update "gc" behavior in commit, merge, am, rebase and index-pack
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- May 15, 2012, 11:25 UTC
- Message-ID
- <CACsJy8AjtE_K53toP6WHh6W9aDSxEur+xOt3wQQ=cDuhBcLuhA@mail.gmail.com>
- In-Reply-To
- <CAGdFq_hneGBtjKHk=jqmgrVgYFKEFYLTnyS+-OemwL4z7JKmKw@mail.gmail.com>
On Mon, May 14, 2012 at 10:18 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 8 quoted lines
> On Mon, May 14, 2012 at 4:09 AM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> 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