git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 5/5] add throughput display to index-pack

From
Nicolas Pitre <nico@cam.org>
Date
Oct 30, 2007, 18:57 UTC
Message-ID
<1193770655-20492-6-git-send-email-nico@cam.org>
In-Reply-To
<1193770655-20492-5-git-send-email-nico@cam.org>

... and call it "Receiving objects" when over stdin to look clearer to end users.

Signed-off-by: Nicolas Pitre <nico@cam.org>
---
 index-pack.c |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/index-pack.c b/index-pack.c
index 879ea15..61ea762 100644
--- a/index-pack.c
+++ b/index-pack.c
@@ -87,6 +87,8 @@ static void *fill(int min)
 				die("early EOF");
 			die("read error on input: %s", strerror(errno));
 		}
+		if (from_stdin)
+			display_throughput(progress, ret);
 		input_len += ret;
 	} while (input_len < min);
 	return input_buffer;
@@ -406,7 +408,9 @@ static void parse_pack_objects(unsigned char *sha1)
 	 * - remember base (SHA1 or offset) for all deltas.
 	 */
 	if (verbose)
-		progress = start_progress("Indexing objects", nr_objects);
+		progress = start_progress(
+				from_stdin ? "Receiving objects" : "Indexing objects",
+				nr_objects);
 	for (i = 0; i < nr_objects; i++) {
 		struct object_entry *obj = &objects[i];
 		data = unpack_raw_entry(obj, &delta->base);
-- 
1.5.3.4.1463.gf79ad2
Previous: Nicolas PitreNext: Nicolas Pitre
Message 6 of 11 in “more progress display stuff”
  1. 0/5 more progress display stuffNicolas Pitre, Oct 30, 2007
  2. 1/5 prune-packed: don't call display_progress() for every fileNicolas Pitre, Oct 30, 2007
  3. 2/5 make struct progress an opaque typeNicolas Pitre, Oct 30, 2007
  4. 3/5 relax usage of the progress APINicolas Pitre, Oct 30, 2007
  5. 4/5 add throughput to progress displayNicolas Pitre, Oct 30, 2007
  6. 5/5 add throughput display to index-packNicolas Pitre, Oct 30, 2007
  7. 6/5 add some copyright notice to the progress display codeNicolas Pitre, Oct 30, 2007
  8. 7/5 add throughput display to git-pushNicolas Pitre, Oct 30, 2007
  9. Junio C HamanoOct 31, 2007
  10. Shawn O. PearceNov 1, 2007
  11. Nicolas PitreNov 1, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.