All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>, Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Stop displaying "Pack pack-$ID created." during git-gc
Date: Fri, 19 Oct 2007 01:03:35 -0400	[thread overview]
Message-ID: <20071019050335.GA17222@spearce.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710182251110.19446@xanadu.home>

Discussion on the list tonight came to the conclusion that showing
the name of the packfile we just created during git-repack is not
a very useful message for any end-user.  For the really technical
folk who need to have the name of the newest packfile they can use
something such as `ls -t .git/objects/pack | head -2` to find the
most recently created packfile.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---

 Nicolas Pitre <nico@cam.org> wrote:
 > On Thu, 18 Oct 2007, Jeff King wrote:
 > >     Can we get rid of total statistics (I think this is useful for some
 > >     power users, but perhaps there should be a verbosity level), the
 > >     name of the pack file (same deal), and the totally useless "Done."?
 >
 > Agreed for the pack name.  Certainly no one cares.

 This makes it so.

 git-repack.sh |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/git-repack.sh b/git-repack.sh
index e72adc4..7220635 100755
--- a/git-repack.sh
+++ b/git-repack.sh
@@ -83,9 +83,6 @@ for name in $names ; do
 	fullbases="$fullbases pack-$name"
 	chmod a-w "$PACKTMP-$name.pack"
 	chmod a-w "$PACKTMP-$name.idx"
-	if test "$quiet" != '-q'; then
-	    echo "Pack pack-$name created."
-	fi
 	mkdir -p "$PACKDIR" || exit
 
 	for sfx in pack idx
-- 
1.5.3.4.1249.g895be

  parent reply	other threads:[~2007-10-19  5:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  0:45 [PATCH] Change 'Deltifying objects' to 'Delta compressing objects' Shawn O. Pearce
2007-10-19  2:12 ` Jeff King
2007-10-19  2:19   ` Sam Vilain
2007-10-19  2:24     ` David Symonds
2007-10-19  2:34       ` Shawn O. Pearce
2007-10-19  3:02         ` Nicolas Pitre
2007-10-19  2:36       ` Jeff King
2007-10-19  2:55         ` Sam Vilain
2007-10-19  2:25     ` Jeff King
2007-10-19  2:21   ` Shawn O. Pearce
2007-10-19  2:34     ` Jeff King
2007-10-19  2:47       ` Shawn O. Pearce
2007-10-19  3:01       ` Nicolas Pitre
2007-10-19  3:07         ` Jeff King
2007-10-19  3:24           ` Nicolas Pitre
2007-10-19  3:32             ` Jeff King
2007-10-19  3:50               ` Nicolas Pitre
2007-10-19  3:56                 ` Jeff King
2007-10-19  4:21                   ` Linus Torvalds
2007-10-19  4:29                     ` Jeff King
2007-10-19 11:58                       ` Nicolas Pitre
2007-10-19 19:00                         ` Linus Torvalds
2007-10-19 21:57                           ` Linus Torvalds
2007-10-19  5:09                 ` Shawn O. Pearce
2007-10-19  3:33             ` Shawn O. Pearce
2007-10-19  5:03         ` Shawn O. Pearce [this message]
2007-10-19  2:49     ` Nicolas Pitre
2007-10-19  3:17       ` Shawn O. Pearce
2007-10-19  3:38         ` Nicolas Pitre
2007-10-19  3:41           ` Jeff King
2007-10-19  3:45           ` Shawn O. Pearce
2007-10-19  4:02             ` Nicolas Pitre
2007-10-19 11:44             ` Wincent Colaiuta
2007-10-19  2:45   ` Nicolas Pitre
2007-10-19  2:59     ` Jeff King
2007-10-19  3:11       ` Nicolas Pitre
2007-10-19  3:15         ` Jeff King
2007-10-19  3:27           ` Nicolas Pitre

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=20071019050335.GA17222@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    /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.