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

Re: [PATCH 2/3] refs: do not label special refs as pseudo refs

From
Patrick Steinhardt <ps@pks.im>
Date
Apr 30, 2024, 07:29 UTC
Message-ID
<ZjCd97dqiHfkm1UG@tanuki>
In-Reply-To
<5322n7eqkov3fqw2zw2seiqyqcmmrlo35camq76n546dkgycru@njuj32gmbogh>
On Mon, Apr 29, 2024 at 05:52:41PM -0500, Justin Tobler wrote:
Show 19 quoted lines
> On 24/04/29 03:41PM, Patrick Steinhardt wrote:
> > diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> > index d71b199955..4275918fa0 100644
> > --- a/Documentation/glossary-content.txt
> > +++ b/Documentation/glossary-content.txt
> > @@ -497,20 +497,28 @@ exclude;;
> >  	unusual refs.
> >  
> >  [[def_pseudoref]]pseudoref::
> > -	Pseudorefs are a class of files under `$GIT_DIR` which behave
> > -	like refs for the purposes of rev-parse, but which are treated
> > -	specially by git.  Pseudorefs both have names that are all-caps,
> > -	and always start with a line consisting of a
> > -	<<def_SHA1,SHA-1>> followed by whitespace.  So, HEAD is not a
> > -	pseudoref, because it is sometimes a symbolic ref.  They might
> 
> We remove the example here about HEAD not being a pseudoref. This
> example seems helpful to indicate that a pseudoref cannot be a symbolic
> ref. Is this no longer the case and the change intended?

I just don't see why we would want to have this restriction. Honestly, the more I think about this whole topic the more I want to go into the direction I've hinted at in the cover letter: drop "special refs" and define pseudo refs as either FETCH_HEAD or MERGE_HEAD. Everything else is just a normal ref, even though some of those may live in the root directory if they conform to a set of strict rules:

  - All upppercase characters plus underscores.
  - Must end with "_HEAD", except a list of known irregular root refs.
I feel like the world would be better like this.
Show 18 quoted lines
> > -	optionally contain some additional data.  `MERGE_HEAD` and
> > -	`CHERRY_PICK_HEAD` are examples.  Unlike
> > -	<<def_per_worktree_ref,per-worktree refs>>, these files cannot
> > -	be symbolic refs, and never have reflogs.  They also cannot be
> > -	updated through the normal ref update machinery.  Instead,
> > -	they are updated by directly writing to the files.  However,
> > -	they can be read as if they were refs, so `git rev-parse
> > -	MERGE_HEAD` will work.
> > +	Pseudorefs are references that live in the root of the reference
> > +	hierarchy, outside of the usual "refs/" hierarchy. Pseudorefs have an
> > +	all-uppercase name and must end with a "_HEAD" suffix, for example
> > +	"`BISECT_HEAD`". Other than that, pseudorefs behave the exact same as
> > +	any other reference and can be both read and written via regular Git
> > +	tooling.
> 
> Pseudorefs behaving the same and using the same tooling seems to
> contridict the previous documentation. I assume the previous information
> was out-of-date, but it might be nice to explain this in the message.

Yes, and I actually want to change this. We never enforced restrictions for pseudorefs anyway, they can be symrefs just fine. And neither would I see any reason why that should be the case in the first place.

Show 8 quoted lines
> > ++
> > +<<def_special_ref>,Special refs>> are not pseudorefs.
> > ++
> > +Due to historic reasons, Git has several irregular pseudo refs that do not
> > +follow above rules. The following list of irregular pseudo refs is exhaustive
> 
> We seem to be inconsistent between using "pseudoref" and "pseudo ref".
> Not sure it we want to be consistent here. 
Makes sense.
Patrick
Show 62 quoted lines
> -Justin
> 
> > +and shall not be extended in the future:
> > +
> > + - "`AUTO_MERGE`"
> > +
> > + - "`BISECT_EXPECTED_REV`"
> > +
> > + - "`NOTES_MERGE_PARTIAL`"
> > +
> > + - "`NOTES_MERGE_REF`"
> > +
> > + - "`MERGE_AUTOSTASH`"
> >  
> >  [[def_pull]]pull::
> >  	Pulling a <<def_branch,branch>> means to <<def_fetch,fetch>> it and
> > diff --git a/refs.c b/refs.c
> > index c64f66bff9..567c6fc6ff 100644
> > --- a/refs.c
> > +++ b/refs.c
> > @@ -905,6 +905,8 @@ int is_pseudoref(struct ref_store *refs, const char *refname)
> >  
> >  	if (!is_pseudoref_syntax(refname))
> >  		return 0;
> > +	if (is_special_ref(refname))
> > +		return 0;
> >  
> >  	if (ends_with(refname, "_HEAD")) {
> >  		refs_resolve_ref_unsafe(refs, refname,
> > diff --git a/t/t6302-for-each-ref-filter.sh b/t/t6302-for-each-ref-filter.sh
> > index 948f1bb5f4..8c92fbde79 100755
> > --- a/t/t6302-for-each-ref-filter.sh
> > +++ b/t/t6302-for-each-ref-filter.sh
> > @@ -52,6 +52,23 @@ test_expect_success '--include-root-refs pattern prints pseudorefs' '
> >  	test_cmp expect actual
> >  '
> >  
> > +test_expect_success '--include-root-refs pattern does not print special refs' '
> > +	test_when_finished "rm -rf repo" &&
> > +	git init repo &&
> > +	(
> > +		cd repo &&
> > +		test_commit initial &&
> > +		git rev-parse HEAD >.git/MERGE_HEAD &&
> > +		git for-each-ref --format="%(refname)" --include-root-refs >actual &&
> > +		cat >expect <<-EOF &&
> > +		HEAD
> > +		$(git symbolic-ref HEAD)
> > +		refs/tags/initial
> > +		EOF
> > +		test_cmp expect actual
> > +	)
> > +'
> > +
> >  test_expect_success '--include-root-refs with other patterns' '
> >  	cat >expect <<-\EOF &&
> >  	HEAD
> > -- 
> > 2.45.0-rc1
> > 
> 
> 
Previous: Justin ToblerNext: Jean-Noël AVILA
Message 14 of 93 in “Clarify pseudo-ref terminology”
  1. 0/3 Clarify pseudo-ref terminologyPatrick Steinhardt, Apr 29, 2024
  2. 1/3 refs: move `is_special_ref()`Patrick Steinhardt, Apr 29, 2024
  3. 2/3 refs: do not label special refs as pseudo refsPatrick Steinhardt, Apr 29, 2024
  4. Phillip WoodApr 29, 2024
  5. Patrick SteinhardtApr 30, 2024
  6. Phillip WoodApr 30, 2024
  7. Patrick SteinhardtApr 30, 2024
  8. Jeff KingApr 30, 2024
  9. Karthik NayakApr 30, 2024
  10. Patrick SteinhardtApr 30, 2024
  11. Patrick SteinhardtApr 30, 2024
  12. Junio C HamanoApr 29, 2024
  13. Justin ToblerApr 29, 2024
  14. Patrick SteinhardtApr 30, 2024
  15. Jean-Noël AVILAMay 9, 2024
  16. Patrick SteinhardtMay 10, 2024
  17. 3/3 refs: fix segfault in `is_pseudoref()` when ref cannot be resolvedPatrick Steinhardt, Apr 29, 2024
  18. Phillip WoodApr 29, 2024
  19. Karthik NayakApr 29, 2024
  20. Phillip WoodApr 29, 2024
  21. Karthik NayakApr 29, 2024
  22. Patrick SteinhardtApr 30, 2024
  23. 00/10 Clarify pseudo-ref terminologyPatrick Steinhardt, Apr 30, 2024
  24. 01/10 Documentation/glossary: redefine pseudorefs as special refsPatrick Steinhardt, Apr 30, 2024
  25. Karthik NayakApr 30, 2024
  26. Justin ToblerApr 30, 2024
  27. Junio C HamanoApr 30, 2024
  28. Patrick SteinhardtMay 2, 2024
  29. 02/10 Documentation/glossary: clarify limitations of pseudorefsPatrick Steinhardt, Apr 30, 2024
  30. Kristoffer HaugsbakkApr 30, 2024
  31. 03/10 Documentation/glossary: define root refs as refsPatrick Steinhardt, Apr 30, 2024
  32. Karthik NayakApr 30, 2024
  33. 04/10 refs: rename `is_pseudoref()` to `is_root_ref()`Patrick Steinhardt, Apr 30, 2024
  34. Junio C HamanoApr 30, 2024
  35. 05/10 refs: refname `is_special_ref()` to `is_pseudo_ref()`Patrick Steinhardt, Apr 30, 2024
  36. Karthik NayakApr 30, 2024
  37. 06/10 refs: classify HEAD as a root refPatrick Steinhardt, Apr 30, 2024
  38. 07/10 refs: root refs can be symbolic refsPatrick Steinhardt, Apr 30, 2024
  39. Justin ToblerApr 30, 2024
  40. Patrick SteinhardtMay 2, 2024
  41. Justin ToblerMay 3, 2024
  42. Patrick SteinhardtMay 7, 2024
  43. 08/10 refs: pseudorefs are no refsPatrick Steinhardt, Apr 30, 2024
  44. 09/10 ref-filter: properly distinuish pseudo and root refsPatrick Steinhardt, Apr 30, 2024
  45. Karthik NayakApr 30, 2024
  46. Patrick SteinhardtMay 2, 2024
  47. Karthik NayakMay 2, 2024
  48. 10/10 refs: refuse to write pseudorefsPatrick Steinhardt, Apr 30, 2024
  49. 00/10 Clarify pseudo-ref terminologyPatrick Steinhardt, May 2, 2024
  50. 01/10 Documentation/glossary: redefine pseudorefs as special refsPatrick Steinhardt, May 2, 2024
  51. 02/10 Documentation/glossary: clarify limitations of pseudorefsPatrick Steinhardt, May 2, 2024
  52. 03/10 Documentation/glossary: define root refs as refsPatrick Steinhardt, May 2, 2024
  53. 04/10 refs: rename `is_pseudoref()` to `is_root_ref()`Patrick Steinhardt, May 2, 2024
  54. 05/10 refs: refname `is_special_ref()` to `is_pseudo_ref()`Patrick Steinhardt, May 2, 2024
  55. 06/10 refs: classify HEAD as a root refPatrick Steinhardt, May 2, 2024
  56. 07/10 refs: root refs can be symbolic refsPatrick Steinhardt, May 2, 2024
  57. Jeff KingMay 3, 2024
  58. Patrick SteinhardtMay 15, 2024
  59. Patrick SteinhardtMay 15, 2024
  60. Jeff KingMay 15, 2024
  61. Patrick SteinhardtMay 15, 2024
  62. Jeff KingMay 15, 2024
  63. Patrick SteinhardtMay 15, 2024
  64. Jeff KingMay 15, 2024
  65. 08/10 refs: pseudorefs are no refsPatrick Steinhardt, May 2, 2024
  66. 09/10 ref-filter: properly distinuish pseudo and root refsPatrick Steinhardt, May 2, 2024
  67. 10/10 refs: refuse to write pseudorefsPatrick Steinhardt, May 2, 2024
  68. 00/10 Clarify pseudo-ref terminologyPatrick Steinhardt, May 10, 2024
  69. 01/10 Documentation/glossary: redefine pseudorefs as special refsPatrick Steinhardt, May 10, 2024
  70. 02/10 Documentation/glossary: clarify limitations of pseudorefsPatrick Steinhardt, May 10, 2024
  71. 03/10 Documentation/glossary: define root refs as refsPatrick Steinhardt, May 10, 2024
  72. 04/10 refs: rename `is_pseudoref()` to `is_root_ref()`Patrick Steinhardt, May 10, 2024
  73. 05/10 refs: refname `is_special_ref()` to `is_pseudo_ref()`Patrick Steinhardt, May 10, 2024
  74. 06/10 refs: root refs can be symbolic refsPatrick Steinhardt, May 10, 2024
  75. 07/10 refs: classify HEAD as a root refPatrick Steinhardt, May 10, 2024
  76. 08/10 refs: pseudorefs are no refsPatrick Steinhardt, May 10, 2024
  77. 09/10 ref-filter: properly distinuish pseudo and root refsPatrick Steinhardt, May 10, 2024
  78. 10/10 refs: refuse to write pseudorefsPatrick Steinhardt, May 10, 2024
  79. Junio C HamanoMay 10, 2024
  80. 00/10 Clarify pseudo-ref terminologyPatrick Steinhardt, May 15, 2024
  81. 01/10 Documentation/glossary: redefine pseudorefs as special refsPatrick Steinhardt, May 15, 2024
  82. 02/10 Documentation/glossary: clarify limitations of pseudorefsPatrick Steinhardt, May 15, 2024
  83. 03/10 Documentation/glossary: define root refs as refsPatrick Steinhardt, May 15, 2024
  84. 04/10 refs: rename `is_pseudoref()` to `is_root_ref()`Patrick Steinhardt, May 15, 2024
  85. 05/10 refs: rename `is_special_ref()` to `is_pseudo_ref()`Patrick Steinhardt, May 15, 2024
  86. 06/10 refs: do not check ref existence in `is_root_ref()`Patrick Steinhardt, May 15, 2024
  87. Justin ToblerMay 15, 2024
  88. Patrick SteinhardtMay 16, 2024
  89. 07/10 refs: classify HEAD as a root refPatrick Steinhardt, May 15, 2024
  90. Justin ToblerMay 15, 2024
  91. 08/10 refs: pseudorefs are no refsPatrick Steinhardt, May 15, 2024
  92. 09/10 ref-filter: properly distinuish pseudo and root refsPatrick Steinhardt, May 15, 2024
  93. 10/10 refs: refuse to write pseudorefsPatrick Steinhardt, May 15, 2024

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.