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

[PATCH v2 0/5] builtin-status submodule summary

From
Ping Yin <pkufranky@gmail.com>
Date
Mar 14, 2008, 15:28 UTC
Message-ID
<1205508521-7407-1-git-send-email-pkufranky@gmail.com>

IMO, git submodule summary is not so useful for me if it's not integrated into git-status. In fact i never use "git submodule summary" directly. git-status with submodule summary support is very useful to help user figure out what is going on in a more global level when cooking the commit message.

So i think this series should go along with the submodule summary series.
The v2 series has following commits adding a new commit for documentation
      git-submodule summary: --for-status option
      builtin-status: submodule summary support
      builtin-status: configurable submodule summary size
      buitin-status: Add tests for submodule summary
      git-status: Mention status.submodulesummary config in the documentation
and diff relative to v1 is (not containing the documetation patch)
diff --git a/t/t7502-status.sh b/t/t7502-status.sh
index a4cd553..33882c9 100755
--- a/t/t7502-status.sh
+++ b/t/t7502-status.sh
@@ -187,9 +187,7 @@ test_expect_success "status submodule summary is disabled by default" '
 	git diff expect output
 '
 
-cd sm &&
-head=$(git rev-parse --verify HEAD | cut -c1-7) &&
-cd ..
+head=$(cd sm && git rev-parse --short=7 --verify HEAD)
 
 cat > expect <<EOF
 # On branch master
diff --git a/wt-status.c b/wt-status.c
index c7cb69c..7a32c51 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -223,7 +223,7 @@ static void wt_status_print_changed(struct wt_status *s)
 }
 static void wt_status_print_submodule_summary(struct wt_status *s)
 {
-	if (wt_status_submodule_summary == 0) return;
+	if (! wt_status_submodule_summary) return;
 	struct child_process sm_summary;
 	char summary_limit[64];
 	sprintf(summary_limit, "%d", wt_status_submodule_summary);
@@ -339,8 +339,6 @@ void wt_status_print(struct wt_status *s)
 	}
 
 	wt_status_print_changed(s);
-	// must flush s->fp since following call will write to s->fp in a child process
-	fflush(s->fp);
 	wt_status_print_submodule_summary(s);
 	wt_status_print_untracked(s);
 
Next: Ping Yin
Message 1 of 8 in “builtin-status submodule summary”
  1. 0/5 builtin-status submodule summaryPing Yin, Mar 14, 2008
  2. 1/5 git-submodule summary: --for-status optionPing Yin, Mar 14, 2008
  3. 2/5 builtin-status: submodule summary supportPing Yin, Mar 14, 2008
  4. 3/5 builtin-status: configurable submodule summary sizePing Yin, Mar 14, 2008
  5. 4/5 buitin-status: Add tests for submodule summaryPing Yin, Mar 14, 2008
  6. 5/5 git-status: Mention status.submodulesummary config in the documentationPing Yin, Mar 14, 2008
  7. Johannes SixtMar 14, 2008
  8. Ping YinMar 14, 2008

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.