All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: git@vger.kernel.org
Subject: [PATCH] Make git-repack explain what it's doing during prune
Date: Thu, 11 Jan 2007 18:46:23 -0800	[thread overview]
Message-ID: <20070112024623.GA9787@midwinter.com> (raw)

git-pack-objects reports its progress as it runs, but as soon as it
finishes and git-repack (with -d option) runs git-prune-packed, the
user is left in the dark about what's going on. That makes git-repack
feel inconsistent: it starts off with a bunch of progress reports then
appears to just sit there for a while before finishing.

Signed-off-by: Steven Grimm <koreth@midwinter.com>
---
 git-repack.sh |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/git-repack.sh b/git-repack.sh
index 375434b..a69d915 100755
--- a/git-repack.sh
+++ b/git-repack.sh
@@ -110,6 +110,9 @@ then
 		  done
 		)
 	fi
+	if test "$quiet" != '-q'; then
+	    echo "Removing unused objects..."
+	fi
 	git-prune-packed
 fi
 
-- 
1.4.4.4.g1295-dirty

             reply	other threads:[~2007-01-12  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  2:46 Steven Grimm [this message]
2007-01-12 22:55 ` [PATCH] Make git-repack explain what it's doing during prune Junio C Hamano

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=20070112024623.GA9787@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.