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

Re: [PATCH v3 2/2] submodule update: continue when a checkout fails

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 9, 2011, 17:21 UTC
Message-ID
<7vlixayl7d.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1307605623-2831-3-git-send-email-iveqy@iveqy.com>
Fredrik Gustafsson <iveqy@iveqy.com> writes:
Show 17 quoted lines
> +				*)
> +					err="${err} \"Failed to $action in submodule path '$path'\""
> ...
> +					err="${err} \"Failed to recurse into submodule path '$path'\""
> +					continue
> +				else
> +					die_with_status $res "Failed to recurse into submodule path '$path'"
> +				fi
> +			fi
>  		fi
>  	done
> +
> +	if test -n "$err"
> +	then
> +		OIFS=$IFS
> +		IFS=';'
> +		for e in $err

Hmm, I do not see anybody concatenating things with semicolons in between... Am I reading a right patch?

Also I am puzzled what the double-quotes around each error message are doing. Are they meant to be shown to the end user?

> +		do
> +			echo $e
Should this go to the standard error output?
> +		done
> +		IFS=$OIFS
> +		die
Do we want to give an extra empty line here with "die"?
Previous: Fredrik GustafssonNext: Fredrik Gustafsson
Message 5 of 6 in “submodule update continue”
  1. 0/2 submodule update continueFredrik Gustafsson, Jun 9, 2011
  2. 1/2 Add new function die_with_statusFredrik Gustafsson, Jun 9, 2011
  3. Junio C HamanoJun 13, 2011
  4. 2/2 submodule update: continue when a checkout failsFredrik Gustafsson, Jun 9, 2011
  5. Junio C HamanoJun 9, 2011
  6. 2/2 submodule update: continue when a checkout failsFredrik Gustafsson, Jun 13, 2011

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.