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

Re: [PATCHv11 1/7] submodule-config: keep update strategy around

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 18, 2016, 19:28 UTC
Message-ID
<xmqq37sphl83.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1455320080-14648-2-git-send-email-sbeller@google.com>
Stefan Beller <sbeller@google.com> writes:
Show 14 quoted lines
> @@ -340,6 +342,16 @@ static int parse_config(const char *var, const char *value, void *data)
>  			free((void *) submodule->url);
>  			submodule->url = xstrdup(value);
>  		}
> +	} else if (!strcmp(item.buf, "update")) {
> +		if (!value)
> +			ret = config_error_nonbool(var);
> +		else if (!me->overwrite &&
> +			 submodule->update_strategy.type != SM_UPDATE_UNSPECIFIED)
> +			warn_multiple_config(me->commit_sha1, submodule->name,
> +					     "update");
> +		else if (parse_submodule_update_strategy(value,
> +			 &submodule->update_strategy) < 0)
> +				die(_("invalid value for %s"), var);

Mental note. This takes "value" that comes from the config API; the pre-context in this hunk treats it as a transient piece of memory and uses xstrdup() on it before storing it away in submodule->url.

Show 14 quoted lines
> +int parse_submodule_update_strategy(const char *value,
> +		struct submodule_update_strategy *dst)
> +{
> +	dst->command = NULL;
> +	if (!strcmp(value, "none"))
> +		dst->type = SM_UPDATE_NONE;
> +	else if (!strcmp(value, "checkout"))
> +		dst->type = SM_UPDATE_CHECKOUT;
> +	else if (!strcmp(value, "rebase"))
> +		dst->type = SM_UPDATE_REBASE;
> +	else if (!strcmp(value, "merge"))
> +		dst->type = SM_UPDATE_MERGE;
> +	else if (skip_prefix(value, "!", &dst->command))
> +		dst->type = SM_UPDATE_COMMAND;

This however uses skip_prefix() on value, making dst->command store a pointer into that transient piece of memory.

That looks inconsistent, doesn't it?  I think this part should be
	else if (value[0] == '!') {
		dst->type = SM_UPDATE_COMMAND;
                dst->command = xstrdup(value + 1);
        }

or something like that. I.e. dst->command should own the piece of memory it points at, no?

Previous: Stefan BellerNext: Stefan Beller
Message 3 of 10 in “[PATCHv11 0/7] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 12, 2016
  2. 1/7 submodule-config: keep update strategy aroundStefan Beller, Feb 12, 2016
  3. Junio C HamanoFeb 18, 2016
  4. 2/7 submodule-config: drop check against NULLStefan Beller, Feb 12, 2016
  5. 3/7 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 12, 2016
  6. 4/7 submodule update: direct error message to stderrStefan Beller, Feb 12, 2016
  7. 5/7 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 12, 2016
  8. 6/7 submodule update: expose parallelism to the userStefan Beller, Feb 12, 2016
  9. 7/7 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 12, 2016
  10. Junio C HamanoFeb 18, 2016

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.