From: Jeff King <peff@peff.net>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] prune: show progress while marking reachable objects
Date: Tue, 8 Nov 2011 00:31:49 -0500 [thread overview]
Message-ID: <20111108053149.GA29643@sigill.intra.peff.net> (raw)
In-Reply-To: <1320494408-6373-1-git-send-email-pclouds@gmail.com>
On Sat, Nov 05, 2011 at 07:00:08PM +0700, Nguyen Thai Ngoc Duy wrote:
> prune already shows progress meter while pruning. The marking part may
> take a few seconds or more, depending on repository size. Show
> progress meter during this time too.
Thanks, this is a nice start. It's missing a few things IMHO:
1. It actually counts commits, not all objects. I'm tempted to say
this doesn't matter, as any eye candy is helpful. Except that the
most common use of prune is as part of "git gc", in which case
pack-objects will have just done the "counting objects" phase and
come up with some number. If we count all objects, then our end
number is the same (modulo any .keep packs, but at least it's
probably in the same order of magnitude). That gives the user a
better sense of completion time.
2. Prune should learn --progress/--no-progress, isatty(2), etc. And
git-gc should pass --no-progress when it's told to be quiet.
Patches for both in a moment.
-Peff
next prev parent reply other threads:[~2011-11-08 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 12:00 [PATCH] prune: show progress while marking reachable objects Nguyễn Thái Ngọc Duy
2011-11-08 5:31 ` Jeff King [this message]
2011-11-08 5:34 ` [PATCH 1/2] prune: handle --progress/no-progress Jeff King
2011-11-09 4:23 ` [PATCH] " Nguyễn Thái Ngọc Duy
2011-11-08 5:37 ` [PATCH 2/2] reachable: per-object progress Jeff King
2011-11-08 5:40 ` [PATCH] prune: show progress while marking reachable objects Junio C Hamano
2011-11-09 4:26 ` Nguyen Thai Ngoc 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111108053149.GA29643@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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.
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 NNTP newsgroup(s).