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

Re: [PATCH] failure with diff --submodule=diff with moved nested submodule HEAD

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 31, 2017, 19:38 UTC
Message-ID
<xmqqk275xmmu.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170331175907.17400-1-sbeller@google.com>
Stefan Beller <sbeller@google.com> writes:
> This fails reliable for me.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---

I take it that this is a WIP for the testing half of the patch you are working on (i.e. you are not just throwing a patch to document known breakage to be fixed later, in which case these would have been _expect_failure).

Thanks.
Show 28 quoted lines
>  t/t4060-diff-submodule-option-diff-format.sh | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/t/t4060-diff-submodule-option-diff-format.sh b/t/t4060-diff-submodule-option-diff-format.sh
> index 7e23b55ea4..89bced3484 100755
> --- a/t/t4060-diff-submodule-option-diff-format.sh
> +++ b/t/t4060-diff-submodule-option-diff-format.sh
> @@ -746,4 +746,20 @@ test_expect_success 'diff --submodule=diff with .git file' '
>  	test_cmp expected actual
>  '
>  
> +test_expect_success 'setup nested submodule' '
> +	git submodule add -f ./sm2 &&
> +	git commit -a -m "add sm2" &&
> +	git -C sm2 submodule add ../sm2 &&
> +	git -C sm2 commit -a -m "nested sub"
> +'
> +
> +test_expect_success 'move nested submodule HEAD' '
> +	git -C sm2/sm2 commit --allow-empty -m "new HEAD"
> +'
> +
> +test_expect_success 'diff --submodule=diff with moved nested submodule HEAD' '
> +	git -C sm2 diff --submodule=diff >actual 2>err &&
> +	test_must_be_empty err
> +'
> +
>  test_done
Previous: Stefan Beller
Message 5 of 5 in “git diff --submodule=diff fails with submodules in a submodule”
  1. David ParrishMar 31, 2017
  2. Stefan BellerMar 31, 2017
  3. Jacob KellerMar 31, 2017
  4. failure with diff --submodule=diff with moved nested submodule HEADStefan Beller, Mar 31, 2017
  5. Junio C HamanoMar 31, 2017

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.