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

Re: [PATCH v4 5/5] git-submodule summary: test

From
Ping Yin <pkufranky@gmail.com>
Date
Mar 11, 2008, 01:57 UTC
Message-ID
<46dff0320803101857t435ec42g93c3605ec64d710a@mail.gmail.com>
In-Reply-To
<1205171657-16216-5-git-send-email-pkufranky@gmail.com>
On Tue, Mar 11, 2008 at 1:54 AM, Ping Yin <pkufranky@gmail.com> wrote:
Show 18 quoted lines
> Signed-off-by: Ping Yin <pkufranky@gmail.com>
>  ---
>   t/t7401-submodule-summary.sh |  194 ++++++++++++++++++++++++++++++++++++++++++
>  +
>  +sleep 1s
>  +head4=$(add_file sm1 foo4 foo5) &&
>  +head4_full=$(GIT_DIR=sm1/.git git rev-parse --verify HEAD)
>  +test_expect_success 'modified submodule(backward and forward)' "
>  +    git submodule summary >actual &&
>  +    diff actual - <<-EOF
>  +* sm1 $head2...$head4 (4):
>  +  > Add foo5
>  +  > Add foo4
>  +  < Add foo3
>  +  < Add foo2
>  +
>  +EOF
>  +"

'sleep 1s' is used to just make sure the summary result just has the same commit order as i expected (the order is undefined if not using this because the commit time are all the same).

However, it seems ugly. I will resend this patch later by using result from 'git log --pretty=format' as the expected result.

>  +
-- 
Ping Yin
Previous: Ping YinNext: Ping Yin
Message 6 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.