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

Re: [PATCH] builtin-revert.c: Make use of merge_recursive()

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 11, 2008, 15:47 UTC
Message-ID
<alpine.DEB.1.00.0808111737270.24820@pacific.mpi-cbg.de.mpi-cbg.de>
In-Reply-To
<1218467003-14591-1-git-send-email-s-beyer@gmx.net>
Hi,
On Mon, 11 Aug 2008, Stephan Beyer wrote:
Show 10 quoted lines
> diff --git a/builtin-merge-recursive.c b/builtin-merge-recursive.c
> index 09aa830..d8bd21f 100644
> --- a/builtin-merge-recursive.c
> +++ b/builtin-merge-recursive.c
> @@ -1327,7 +1327,7 @@ static const char *better_branch_name(const char *branch)
>  	return name ? name : branch;
>  }
>  
> -static struct commit *get_ref(const char *ref)
> +struct commit *get_ref(const char *ref)

The name get_ref() is way too generic to be non-static. But I have a hunch that peel_to_type() does a lot of what we want here, if not all of it.

Show 26 quoted lines
> diff --git a/builtin-revert.c b/builtin-revert.c
> index 27881e9..c54cf8a 100644
> --- a/builtin-revert.c
> +++ b/builtin-revert.c
> @@ -219,15 +216,21 @@ static int merge_recursive(const char *base_sha1,
>  	 * and $prev on top of us (when reverting), or the change between
>  	 * $prev and $commit on top of us (when cherry-picking or replaying).
>  	 */
> -	argv[i++] = "merge-recursive";
> -	if (base_sha1)
> -		argv[i++] = base_sha1;
> -	argv[i++] = "--";
> -	argv[i++] = head_sha1;
> -	argv[i++] = next_sha1;
> -	argv[i++] = NULL;
> -
> -	return run_command_v_opt(argv, RUN_COMMAND_NO_STDIN | RUN_GIT_CMD);
> +	if (base_sha1) {
> +		struct commit *base = get_ref(base_sha1);
> +		commit_list_insert(base, &ca);
> +	}
> +	h1 = get_ref(head_sha1);
> +	h2 = get_ref(next_sha1);
> +
> +	index_fd = hold_locked_index(lock, 1);
> +	clean = merge_recursive(h1, h2, head_name, next_name, ca, &result);
h1 and h2 are not expressive.  head_commit and next_commit would be.

Rest looks good to me -- even if I had to spend too much time (therefore being not really thorough in the end) verifying that merge_recursive() does not lock the index itself, and that GITHEAD_* definitions are not necessary anymore, since merge_recursive() takes the arguments directly; you might want to make it easier for this reviewer in the future, if you want this reviewer to review your patches, that is.

Ciao, Dscho

Previous: Stephan BeyerNext: Stephan Beyer
Message 14 of 38 in “Avoid run_command() for recursive in builtin-merge”
  1. 0/2 Avoid run_command() for recursive in builtin-mergeMiklos Vajna, Aug 10, 2008
  2. 1/2 merge-recursive: prepare merge_recursive() to be called from builtinsMiklos Vajna, Aug 10, 2008
  3. 2/2 builtin-merge: avoid run_command_v_opt() for recursiveMiklos Vajna, Aug 10, 2008
  4. Junio C HamanoAug 11, 2008
  5. Miklos VajnaAug 11, 2008
  6. Junio C HamanoAug 11, 2008
  7. Miklos VajnaAug 11, 2008
  8. Add a new test to ensure merging a submodule is handled properly.Miklos Vajna, Aug 11, 2008
  9. Stephan BeyerAug 11, 2008
  10. Miklos VajnaAug 11, 2008
  11. Junio C HamanoAug 11, 2008
  12. Stephan BeyerAug 11, 2008
  13. builtin-revert.c: Make use of merge_recursive()Stephan Beyer, Aug 11, 2008
  14. Johannes SchindelinAug 11, 2008
  15. Stephan BeyerAug 11, 2008
  16. Miklos VajnaAug 11, 2008
  17. builtin-revert: Make use of merge_recursive()Stephan Beyer, Aug 11, 2008
  18. Stephan BeyerAug 11, 2008
  19. Junio C HamanoAug 11, 2008
  20. Junio C HamanoAug 11, 2008
  21. Stephan BeyerAug 11, 2008
  22. Junio C HamanoAug 11, 2008
  23. Split out merge_recursive() to merge-recursive.cMiklos Vajna, Aug 12, 2008
  24. Stephan BeyerAug 12, 2008
  25. Miklos VajnaAug 12, 2008
  26. merge-recursive.c: Add more generic merge_recursive_generic()Stephan Beyer, Aug 12, 2008
  27. Make builtin-revert.c use merge_recursive_generic()Stephan Beyer, Aug 12, 2008
  28. Miklos VajnaAug 12, 2008
  29. Stephan BeyerAug 13, 2008
  30. Miklos VajnaAug 13, 2008
  31. Daniel BarkalowAug 13, 2008
  32. Stephan BeyerAug 13, 2008
  33. Daniel BarkalowAug 13, 2008
  34. Junio C HamanoAug 13, 2008
  35. Stephan BeyerAug 13, 2008
  36. Daniel BarkalowAug 13, 2008
  37. Junio C HamanoAug 13, 2008
  38. Junio C HamanoAug 14, 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.