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

Re: [GSoC PATCH v2 3/4] repo: add path.gitdir with absolute and relative suffix formatting

From
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date
Jun 8, 2026, 22:17 UTC
Message-ID
<D14CA105-3690-4BB1-932D-7081B1A1DBFA@gmail.com>
In-Reply-To
<20260605163012.181089-4-jayatheerthkulkarni2005@gmail.com>
Show 5 quoted lines
> +test_repo_info_path () {
> + field_name=$1
> + expect_absolute_eval=$2
> + expect_relative=$3
> + env_prefix=$4
This helper function needs a documentation.
> + test_expect_success "query individual key: path.$field_name.absolute${env_prefix:+ ($env_prefix)}" '
This makes the output polluted. What about changing it by something like:
	test_expect_success "absolute: $label' '...'
	test_expect_success "relative: $label' '...'
with a custom label?
Show 5 quoted lines
> +
> +test_expect_success 'setup test repository layout for path fields' '
> + git init test-repo &&
> + mkdir -p test-repo/sub
> +'

The helper function `test_repo_info_path` is relying too much on the existence of the `test-repo`. I think it would be better to add a new parameter `repo_name` (or similar) because:

1. You could move this creation to the helper function and
   you won't need to place the test after that creation
2. You could use different for each (test_repo_info_path call, path format)
   pair. Currently, if more than one test fails, its result is overwritten
   and the `expect` and `actual` files from the trash directory will be
   the last of the broken tests.
3. You won't need to use the hacky 'echo "$(cd .. && pwd)' 
This applies my suggestions (feel free to use, adapt or discard it):
test_repo_info_path () {
        label=$1
	field_name=$2
	repo_name=$3
	expect_absolute=$4
	expect_relative=$5
	init_command=$6
	absolute_root="$repo_name"-absolute
	relative_root="$repo_name"-relative
	expect_absolute="$PWD"/"$absolute_root"/"$expect_absolute"
	test_expect_success 'setup test repository layout for path fields' '
		git init "$absolute_root" &&
		git init "$relative_root" &&
	       	mkdir -p "$absolute_root"/sub "$relative_root"/sub
	'
	test_expect_success "absolute: $label" '
		(
			export ROOT="$PWD"/"$absolute_root" &&
			cd "$absolute_root"/sub &&
			eval "$init_command" &&
			echo "path.$field_name.absolute=$expect_absolute" >expect &&
			git repo info path.$field_name.absolute >actual &&
			test_cmp expect actual
		)
	'
	test_expect_success "relative: $label" '
		(
			export ROOT="$PWD"/"$relative_root" &&
			cd "$relative_root"/sub &&
			eval "$init_command" &&
			echo "path.$field_name.relative=$expect_relative" >expect &&
			git repo info path.$field_name.relative >actual &&
			test_cmp expect actual
		)
	'
}
test_repo_info_path 'gitdir' 'gitdir' 'gitdir' '.git' '../.git'
Previous: K JayatheerthNext: K Jayatheerth
Message 29 of 82 in “teach git repo info to handle path keys”
  1. K JayatheerthJun 1, 2026
  2. [GSoC][PATCH 1/4] path: add strbuf_add_path for formatting pathsK Jayatheerth, Jun 1, 2026
  3. Phillip WoodJun 2, 2026
  4. [GSoC][PATCH 2/4] rev-parse: use strbuf_add_path for path formattingK Jayatheerth, Jun 1, 2026
  5. [GSoC][PATCH 3/4] repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 1, 2026
  6. Lucas Seiki OshiroJun 1, 2026
  7. Junio C HamanoJun 1, 2026
  8. [GSoC][PATCH 4/4] repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 1, 2026
  9. Lucas Seiki OshiroJun 1, 2026
  10. Lucas Seiki OshiroJun 1, 2026
  11. Lucas Seiki OshiroJun 1, 2026
  12. Lucas Seiki OshiroJun 1, 2026
  13. Junio C HamanoJun 1, 2026
  14. Phillip WoodJun 2, 2026
  15. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 5, 2026
  16. 1/4 path: introduce format_path() for centralized path formattingK Jayatheerth, Jun 5, 2026
  17. Kristoffer HaugsbakkJun 5, 2026
  18. K JayatheerthJun 9, 2026
  19. Lucas Seiki OshiroJun 8, 2026
  20. K JayatheerthJun 9, 2026
  21. Justin ToblerJun 8, 2026
  22. 2/4 rev-parse: use format_path for path formattingK Jayatheerth, Jun 5, 2026
  23. Justin ToblerJun 8, 2026
  24. 3/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 5, 2026
  25. Justin ToblerJun 8, 2026
  26. K JayatheerthJun 9, 2026
  27. Justin ToblerJun 9, 2026
  28. K JayatheerthJun 10, 2026
  29. Lucas Seiki OshiroJun 8, 2026
  30. 4/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 5, 2026
  31. Lucas Seiki OshiroJun 8, 2026
  32. Lucas Seiki OshiroJun 5, 2026
  33. K JayatheerthJun 9, 2026
  34. Junio C HamanoJun 8, 2026
  35. K JayatheerthJun 9, 2026
  36. Lucas Seiki OshiroJun 10, 2026
  37. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 12, 2026
  38. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 12, 2026
  39. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 12, 2026
  40. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 12, 2026
  41. Lucas Seiki OshiroJun 15, 2026
  42. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 12, 2026
  43. Lucas Seiki OshiroJun 15, 2026
  44. Lucas Seiki OshiroJun 15, 2026
  45. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 15, 2026
  46. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 15, 2026
  47. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 15, 2026
  48. Justin ToblerJun 15, 2026
  49. K JayatheerthJun 16, 2026
  50. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 15, 2026
  51. Justin ToblerJun 15, 2026
  52. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 15, 2026
  53. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 16, 2026
  54. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 16, 2026
  55. Phillip WoodJun 16, 2026
  56. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 16, 2026
  57. Phillip WoodJun 16, 2026
  58. K JayatheerthJun 16, 2026
  59. Phillip WoodJun 16, 2026
  60. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 16, 2026
  61. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 16, 2026
  62. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 20, 2026
  63. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 20, 2026
  64. Junio C HamanoJun 20, 2026
  65. K JayatheerthJun 20, 2026
  66. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 20, 2026
  67. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 20, 2026
  68. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 20, 2026
  69. 0/3 teach git repo info to handle path keysK Jayatheerth, Jun 21, 2026
  70. 1/3 path: extract append_formatted_path() and use in rev-parseK Jayatheerth, Jun 21, 2026
  71. Junio C HamanoJun 21, 2026
  72. Junio C HamanoJun 22, 2026
  73. K JayatheerthJun 22, 2026
  74. Phillip WoodJun 23, 2026
  75. K JayatheerthJun 24, 2026
  76. 2/3 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 21, 2026
  77. 3/3 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 21, 2026
  78. 0/3 teach git repo info to handle path keysK Jayatheerth, Jun 24, 2026
  79. 1/3 path: extract format_path() and use in rev-parseK Jayatheerth, Jun 24, 2026
  80. Junio C HamanoJun 24, 2026
  81. 2/3 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 24, 2026
  82. 3/3 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 24, 2026

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.