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

Re: [PATCH v3 3/3] diff --submodule=diff: Don't print failure message twice

From
David Turner <novalis@novalis.org>
Date
Aug 30, 2021, 13:45 UTC
Message-ID
<d14d2c180f59b9115754318e4d3567a404769d06.camel@novalis.org>
In-Reply-To
<20210812001332.715876-3-dturner@twosigma.com>

I keep seeing these as "will merge to next?" in the "what's cooking" emails. But I don't see any direct replies, and they don't seem to be merged. Is there something I need to do to get these merged?

Thanks.
On Wed, 2021-08-11 at 20:13 -0400, David Turner wrote:
Show 28 quoted lines
> When we fail to start a diff command inside a submodule, immediately
> exit the routine rather than trying to finish the command and
> printing
> a second message.
> 
> Signed-off-by: David Turner <dturner@twosigma.com>
> ---
>  submodule.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/submodule.c b/submodule.c
> index d13d103975..2e98e840af 100644
> --- a/submodule.c
> +++ b/submodule.c
> @@ -720,8 +720,10 @@ void show_submodule_inline_diff(struct
> diff_options *o, const char *path,
>                 strvec_push(&cp.env_array, GIT_WORK_TREE_ENVIRONMENT
> "=.");
>         }
>  
> -       if (start_command(&cp))
> +       if (start_command(&cp)) {
>                 diff_emit_submodule_error(o, "(diff failed)\n");
> +               goto done;
> +       }
>  
>         while (strbuf_getwholeline_fd(&sb, cp.out, '\n') != EOF)
>                 diff_emit_submodule_pipethrough(o, sb.buf, sb.len);
Previous: David TurnerNext: David Turner
Message 3 of 4 in “Remove unused var”
  1. 1/3 Remove unused varDavid Turner, Aug 12, 2021
  2. 3/3 diff --submodule=diff: Don't print failure message twiceDavid Turner, Aug 12, 2021
  3. David TurnerAug 30, 2021
  4. 2/3 diff --submodule=diff: do not fail on ever-initialied deleted submodulesDavid Turner, Aug 12, 2021

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.