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

Re: [PATCH v4 2/5] git-submodule summary: show commit summary

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 11, 2008, 07:28 UTC
Message-ID
<7vod9ld8iu.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1205171657-16216-2-git-send-email-pkufranky@gmail.com>
Ping Yin <pkufranky@gmail.com> writes:
> This patch does the hard work to show submodule commit summary.
> ...

I've spent considerable amount of time cleaning up your commit log messages for the entire series from the last round when I queued them to 'pu', but you seem to have discarded all of them. As I do not have time to waste doing clean-ups only to have others to discard, and I do not have infinite amount of time, I won't be replacing them with this series tonight.

> Signed-off-by: Ping Yin <pkufranky@gmail.com>

And you did not describe anything about the improvements from the previous round anywhere. interdiff shows that this part is somewhat different:

Show 9 quoted lines
> +		then
> +			case "$mod_dst" in
> +				160000)
> +				sha1_dst=$(GIT_DIR="$name/.git" git rev-parse HEAD)
> +				;;
> +				100644)
> +				sha1_dst=$(git hash-object $name)
> +				;;
> +			esac

Earlier, you were ignoring the one that is not checked out anymore, but now you blindly assume "rev-parse HEAD" to give you a usable sha1_dst. Why?

If a path that previously was a module is changed to a symlink, what happens?

Previous: Ping YinNext: Ping Yin
Message 9 of 10 in “git-submodule summary: code framework”
  1. 1/5 git-submodule summary: code frameworkPing Yin, Mar 10, 2008
  2. 2/5 git-submodule summary: show commit summaryPing Yin, Mar 10, 2008
  3. 3/5 git-submodule summary: limit summary sizePing Yin, Mar 10, 2008
  4. 4/5 git-submodule summary: documentationPing Yin, Mar 10, 2008
  5. 5/5 git-submodule summary: testPing Yin, Mar 10, 2008
  6. Ping YinMar 11, 2008
  7. Ping YinMar 10, 2008
  8. Ping YinMar 11, 2008
  9. Junio C HamanoMar 11, 2008
  10. Ping YinMar 11, 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.