From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>, Fernando Vezzosi <buccia@repnz.net>
Subject: Re: [PATCH] Update "gc" behavior in commit, merge, am, rebase and index-pack
Date: Tue, 15 May 2012 18:25:39 +0700 [thread overview]
Message-ID: <CACsJy8AjtE_K53toP6WHh6W9aDSxEur+xOt3wQQ=cDuhBcLuhA@mail.gmail.com> (raw)
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:
> 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
next prev parent reply other threads:[~2012-05-15 11:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 8:08 [PATCH] Update "gc" behavior in commit, merge, am, rebase and index-pack Nguyễn Thái Ngọc Duy
2012-05-12 8:18 ` Nguyen Thai Ngoc Duy
2012-05-12 17:36 ` Nicolas Pitre
2012-05-14 9:09 ` Nguyen Thai Ngoc Duy
2012-05-14 15:18 ` Sverre Rabbelier
2012-05-15 11:25 ` Nguyen Thai Ngoc Duy [this message]
2012-05-14 20:11 ` Jeff King
2012-05-14 20:50 ` Jeff King
2012-05-14 23:35 ` Junio C Hamano
2012-05-16 12:29 ` [PATCH v2 0/5] "git gc --auto" update Nguyễn Thái Ngọc Duy
2012-05-16 12:29 ` [PATCH v2 1/5] Add convenient function to do automatic garbage collection Nguyễn Thái Ngọc Duy
2012-05-18 22:37 ` Junio C Hamano
2012-05-19 4:56 ` Nguyen Thai Ngoc Duy
2012-05-16 12:29 ` [PATCH v2 2/5] index-pack: perform automatic gc, share receive.gc config with receive-pack Nguyễn Thái Ngọc Duy
2012-05-16 12:29 ` [PATCH v2 3/5] commit: reinstate "gc --auto" Nguyễn Thái Ngọc Duy
2012-05-16 12:29 ` [PATCH v2 4/5] gc: add --dry-run Nguyễn Thái Ngọc Duy
2012-05-16 12:29 ` [PATCH v2 5/5] Update "gc" behavior in commit, merge, am and rebase Nguyễn Thái Ngọc Duy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8AjtE_K53toP6WHh6W9aDSxEur+xOt3wQQ=cDuhBcLuhA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=buccia@repnz.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.net \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).