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

Re: [PATCH v4 1/3] ref-filter: add worktreepath atom

From
Jeff King <peff@peff.net>
Date
Jan 3, 2019, 05:40 UTC
Message-ID
<20190103054043.GG20047@sigill.intra.peff.net>
In-Reply-To
<20181224084756.49952-2-nbelakovski@gmail.com>
On Mon, Dec 24, 2018 at 12:47:54AM -0800, nbelakovski@gmail.com wrote:
> [...]

Thanks for keeping with this. I think we're getting quite close, though I did find a few small-ish issues.

Show 6 quoted lines
> @@ -34,6 +36,8 @@ static struct ref_msg {
>  	"ahead %d, behind %d"
>  };
>  
> +static struct worktree **worktrees;
> +

Maybe define this near "struct hashmap ref_to_worktree_map" so it's more obvious that the two are related?

Show 8 quoted lines
> @@ -75,6 +79,11 @@ static struct expand_data {
>  	struct object_info info;
>  } oi, oi_deref;
>  
> +struct ref_to_worktree_entry {
> +    struct hashmap_entry ent; /* must be the first member! */
> +    struct worktree *wt; /* key is wt->head_ref */
> +};
Indent with spaces?
> -static int used_atom_cnt, need_tagged, need_symref;
> +static int used_atom_cnt, need_tagged, need_symref, has_worktree;
> +static struct hashmap ref_to_worktree_map;

Makes sense. I thought at first has_worktree was a flag that we might care about between parsing and formatting, but it's really just a flag to say "we lazy-loaded the worktree list".

Show 6 quoted lines
> +static int worktree_hashmap_cmpfnc(const void *unused_lookupdata, const void *existing_hashmap_entry_to_test,
> +				   const void *unused_key, const void *keydata_aka_refname)
> +{
> +	const struct ref_to_worktree_entry *e = existing_hashmap_entry_to_test;
> +	return strcmp(e->wt->head_ref, keydata_aka_refname);
> +}
So from the discussion in the cover letter, this needs to be more like:
  static int worktree_hashmap_cmpfnc(const void *unused_lookupdata,
                                     const void *ve1, const void *ve2,
				     const void *keydata_aka_refname)
  {
	const struct ref_to_worktree_entry *e1 = ve1, *e2 = ve2;
	return strcmp(e1->wt->head_ref, keydata_aka_refname ?
		                        keydata_aka_refname :
					e2->wt->head_ref);
  }
Show 8 quoted lines
> +static int worktree_atom_parser(const struct ref_format *format,
> +				struct used_atom *atom,
> +				const char *arg,
> +				struct strbuf *unused_err)
> +{
> +	int i;
> +	if (has_worktree)
> +		return 0;

Minor style nit, but please put a space between the declarations and the start of the code (not strictly necessary for a short function which has no other linebreaks, like the cmpfunc above, but here I think it's confusing not to).

Show 14 quoted lines
> +	worktrees = get_worktrees(0);
> +
> +	hashmap_init(&ref_to_worktree_map, worktree_hashmap_cmpfnc, NULL, 0);
> +
> +	for (i = 0; worktrees[i]; i++) {
> +		if (worktrees[i]->head_ref) {
> +			struct ref_to_worktree_entry *entry;
> +			entry = xmalloc(sizeof(*entry));
> +			entry->wt = worktrees[i];
> +			hashmap_entry_init(entry, strhash(worktrees[i]->head_ref));
> +
> +			hashmap_add(&ref_to_worktree_map, entry);
> +		}
> +	}
Makes sense to load the map.
Show 13 quoted lines
> +static const char *get_worktree_path(const struct used_atom *atom, const struct ref_array_item *ref)
> +{
> +	struct strbuf val = STRBUF_INIT;
> +	struct hashmap_entry entry;
> +	struct ref_to_worktree_entry *lookup_result;
> +
> +	hashmap_entry_init(&entry, strhash(ref->refname));
> +	lookup_result = hashmap_get(&ref_to_worktree_map, &entry, ref->refname);
> +
> +	strbuf_addstr(&val, lookup_result ? lookup_result->wt->path : "");
> +
> +	return strbuf_detach(&val, NULL);
> +}
And that makes sense to look up an item in it. Good.

Adding an empty string to a strbuf is a noop, so that part might more clearly be written as just:

  if (lookup_result)
	strbuf_addstr(&val, lookup_result->wt->path);

We return a "const char *" here, but the result is always allocated. Do we leak the result? Or should this return a "char *"?

I think there are a lot of other atoms that leak currently, but that is being fixed in another topic that is currently in pu.

Show 9 quoted lines
> @@ -2020,6 +2085,11 @@ void ref_array_clear(struct ref_array *array)
>  		free_array_item(array->items[i]);
>  	FREE_AND_NULL(array->items);
>  	array->nr = array->alloc = 0;
> +	if (has_worktree)
> +	{
> +		hashmap_free(&ref_to_worktree_map, 1);
> +		free_worktrees(worktrees);
> +	}

Here we free everything, but we don't unset has_worktree. So anybody trying to format more refs afterward would see our freed worktree list.

We probably want:
  has_worktree = 0;

here. Or simpler still, I think get_worktrees() will always return a non-NULL list (even if it is empty). So you could just drop has_worktree entirely, and use:

  if (worktrees)
	return; /* already loaded */;
in the loading function, and:
  free_worktrees(worktrees);
  worktrees = NULL;
here.
Show 11 quoted lines
> +test_expect_success '"add" a worktree' '
> +	mkdir worktree_dir &&
> +	git worktree add -b master_worktree worktree_dir master
> +'
> +
> +test_expect_success 'validate worktree atom' '
> +	{
> +	echo master: $PWD &&
> +	echo master_worktree: $PWD/worktree_dir &&
> +	echo side: not checked out
> +	} > expect &&
Minor style nit: use "} >expect" without the extra space.

This checks the actual directories. Good. I can never remember the rules for when to use $PWD versus $(pwd) on Windows. We may run afoul of the distinction here.

-Peff
Previous: nbelakovski@gmail.comNext: Eric Sunshine
Message 41 of 125 in “branch: colorize branches checked out in a linked working tree the same way as the current branch is colorized”
  1. branch: colorize branches checked out in a linked working tree the same way as the current branch is colorizedNickolai Belakovski, Sep 27, 2018
  2. Ævar Arnfjörð BjarmasonSep 27, 2018
  3. Nickolai BelakovskiSep 27, 2018
  4. Duy NguyenSep 27, 2018
  5. Jeff KingSep 27, 2018
  6. Nickolai BelakovskiSep 27, 2018
  7. Jeff KingSep 27, 2018
  8. Rafael AscensãoSep 27, 2018
  9. Jeff KingSep 27, 2018
  10. Jeff KingSep 27, 2018
  11. Junio C HamanoSep 27, 2018
  12. Jeff KingSep 28, 2018
  13. Junio C HamanoSep 28, 2018
  14. Rafael AscensãoSep 27, 2018
  15. Jeff KingSep 28, 2018
  16. Ævar Arnfjörð BjarmasonSep 27, 2018
  17. Nickolai BelakovskiSep 27, 2018
  18. Rafael AscensãoSep 27, 2018
  19. 0/2 refactoring branch colorization to ref-filternbelakovski@gmail.com, Nov 11, 2018
  20. 1/2 ref-filter: add worktree atomnbelakovski@gmail.com, Nov 11, 2018
  21. Junio C HamanoNov 12, 2018
  22. Jeff KingNov 12, 2018
  23. Junio C HamanoNov 13, 2018
  24. Nickolai BelakovskiNov 21, 2018
  25. Jeff KingNov 21, 2018
  26. Jeff KingNov 12, 2018
  27. 2/2 branch: Mark and colorize a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Nov 11, 2018
  28. Junio C HamanoNov 12, 2018
  29. Jeff KingNov 12, 2018
  30. Rafael AscensãoNov 12, 2018
  31. Junio C HamanoNov 13, 2018
  32. Jeff KingNov 13, 2018
  33. Nickolai BelakovskiNov 21, 2018
  34. 0/3 nbelakovski@gmail.com, Dec 16, 2018
  35. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Dec 16, 2018
  36. Jeff KingDec 18, 2018
  37. Nickolai BelakovskiDec 20, 2018
  38. Jeff KingDec 20, 2018
  39. 0/3 nbelakovski@gmail.com, Dec 24, 2018
  40. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Dec 24, 2018
  41. Jeff KingJan 3, 2019
  42. Eric SunshineJan 3, 2019
  43. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Dec 24, 2018
  44. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Dec 24, 2018
  45. Jeff KingJan 3, 2019
  46. Jeff KingJan 3, 2019
  47. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Dec 16, 2018
  48. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Dec 16, 2018
  49. Jeff KingDec 18, 2018
  50. 0/3 nbelakovski@gmail.com, Jan 6, 2019
  51. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Jan 6, 2019
  52. Junio C HamanoJan 7, 2019
  53. Nickolai BelakovskiJan 18, 2019
  54. Nickolai BelakovskiJan 18, 2019
  55. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Jan 6, 2019
  56. Junio C HamanoJan 7, 2019
  57. Philip OakleyJan 10, 2019
  58. Nickolai BelakovskiJan 13, 2019
  59. Junio C HamanoJan 14, 2019
  60. Nickolai BelakovskiJan 18, 2019
  61. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Jan 6, 2019
  62. Junio C HamanoJan 7, 2019
  63. 0/3 nbelakovski@gmail.com, Jan 22, 2019
  64. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Jan 22, 2019
  65. Junio C HamanoJan 23, 2019
  66. Nickolai BelakovskiJan 23, 2019
  67. Junio C HamanoJan 24, 2019
  68. Jeff KingJan 24, 2019
  69. Junio C HamanoJan 24, 2019
  70. Jeff KingJan 24, 2019
  71. Junio C HamanoJan 24, 2019
  72. Jeff KingJan 24, 2019
  73. Nickolai BelakovskiJan 31, 2019
  74. Jeff KingJan 31, 2019
  75. Junio C HamanoJan 31, 2019
  76. Jeff KingJan 31, 2019
  77. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Jan 22, 2019
  78. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Jan 22, 2019
  79. 0/3 nbelakovski@gmail.com, Feb 1, 2019
  80. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Feb 1, 2019
  81. Eric SunshineFeb 1, 2019
  82. Nickolai BelakovskiFeb 1, 2019
  83. Junio C HamanoFeb 4, 2019
  84. Nickolai BelakovskiFeb 18, 2019
  85. Junio C HamanoFeb 1, 2019
  86. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Feb 1, 2019
  87. Junio C HamanoFeb 1, 2019
  88. Nickolai BelakovskiFeb 1, 2019
  89. Junio C HamanoFeb 4, 2019
  90. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Feb 1, 2019
  91. Eric SunshineFeb 1, 2019
  92. Nickolai BelakovskiFeb 1, 2019
  93. Junio C HamanoFeb 1, 2019
  94. Nickolai BelakovskiFeb 1, 2019
  95. [RFC] Sample of test for git branch -vvnbelakovski@gmail.com, Feb 2, 2019
  96. Junio C HamanoFeb 1, 2019
  97. Nickolai BelakovskiFeb 1, 2019
  98. 0/3 nbelakovski@gmail.com, Feb 19, 2019
  99. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Feb 19, 2019
  100. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Feb 19, 2019
  101. Jeff KingFeb 21, 2019
  102. Nickolai BelakovskiMar 14, 2019
  103. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Feb 19, 2019
  104. Jeff KingFeb 21, 2019
  105. Nickolai BelakovskiMar 14, 2019
  106. Junio C HamanoMar 18, 2019
  107. Jeff KingFeb 21, 2019
  108. Nickolai BelakovskiMar 14, 2019
  109. 0/3 nbelakovski@gmail.com, Mar 16, 2019
  110. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Mar 16, 2019
  111. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Mar 16, 2019
  112. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Mar 16, 2019
  113. SZEDER GáborMar 18, 2019
  114. Junio C HamanoMar 18, 2019
  115. 0/3 nbelakovski@gmail.com, Apr 29, 2019
  116. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Apr 29, 2019
  117. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Apr 29, 2019
  118. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Apr 29, 2019
  119. SZEDER GáborApr 29, 2019
  120. Nickolai BelakovskiApr 29, 2019
  121. Johannes SchindelinApr 29, 2019
  122. Nickolai BelakovskiApr 29, 2019
  123. Ævar Arnfjörð BjarmasonSep 27, 2018
  124. Johannes SchindelinOct 2, 2018
  125. Johannes SchindelinApr 30, 2019

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.