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

[PATCH v3 5/6] Documentation/git-update-ref.txt: discuss symbolic refs

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Oct 21, 2024, 20:47 UTC
Message-ID
<5033ec82586691065504e429d0c21464abee945a.1729543007.git.code@khaugsbakk.name>
In-Reply-To
<cover.1729543007.git.code@khaugsbakk.name>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Add a paragraph which just emphasizes that the command without any options does not support refs in the final arguments. This is clear already from the names `<new-oid>` and `<old-oid>` but the right balance of redundancy makes documentation robust against stray interpretation.

This is also a good place to mention why `--stdin` has those `symref-*` commands.

Suggested-by: Bence Ferdinandy <bence@ferdinandy.com>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
    v2:
    • Message: grammar: “robust against”
    • Message: Apparently the first paragraph wasn’t wrapped properly
    • Fix “the the”
    • Credit Bence for this suggestion which I forgot to do in v1
    
      Link: https://lore.kernel.org/git/D4U30MD29CJT.3US5SBR598DVY@ferdinandy.com/
    • Message: “symbolic refs”, not links
 Documentation/git-update-ref.txt | 6 ++++++
 1 file changed, 6 insertions(+)
diff --git a/Documentation/git-update-ref.txt b/Documentation/git-update-ref.txt
index 61647ee8413..2e85f7ce3ee 100644
--- a/Documentation/git-update-ref.txt
+++ b/Documentation/git-update-ref.txt
@@ -25,6 +25,12 @@ value is <old-oid>.  You can specify 40 "0" or an empty string
 as <old-oid> to make sure that the ref you are creating does
 not exist.
 
+The final arguments are object names; this command without any options
+does not support updating a symbolic ref to point to another ref (see
+linkgit:git-symbolic-ref[1]).  But `git update-ref --stdin` does have
+the `symref-*` commands so that regular refs and symbolic refs can be
+committed in the same transaction.
+
 If --no-deref is given, <ref> itself is overwritten, rather than
 the result of following the symbolic pointers.
 
-- 
2.46.1.641.g54e7913fcb6
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 51 of 54 in “ref: with git update-ref?”
  1. Bence FerdinandyOct 11, 2024
  2. Kristoffer HaugsbakkOct 11, 2024
  3. Bence FerdinandyOct 11, 2024
  4. Junio C HamanoOct 11, 2024
  5. Bence FerdinandyOct 12, 2024
  6. Phillip WoodOct 13, 2024
  7. Kristoffer HaugsbakkOct 13, 2024
  8. karthik nayakOct 13, 2024
  9. Kristoffer HaugsbakkOct 13, 2024
  10. Bence FerdinandyOct 13, 2024
  11. Kristoffer HaugsbakkOct 14, 2024
  12. 0/6 doc: update-ref: amend old material and discuss symrefskristofferhaugsbakk@fastmail.com, Oct 15, 2024
  13. 1/6 doc: update-ref: drop “flag”kristofferhaugsbakk@fastmail.com, Oct 15, 2024
  14. Taylor BlauOct 16, 2024
  15. Eric SunshineOct 16, 2024
  16. Taylor BlauOct 16, 2024
  17. Kristoffer HaugsbakkOct 17, 2024
  18. Eric SunshineOct 17, 2024
  19. Taylor BlauOct 17, 2024
  20. 2/6 doc: update-ref: remove safety paragraphskristofferhaugsbakk@fastmail.com, Oct 15, 2024
  21. Taylor BlauOct 16, 2024
  22. 3/6 doc: update-ref: demote symlink to last sectionkristofferhaugsbakk@fastmail.com, Oct 15, 2024
  23. 4/6 doc: update-ref: remove confusing paragraphkristofferhaugsbakk@fastmail.com, Oct 15, 2024
  24. Taylor BlauOct 16, 2024
  25. Kristoffer HaugsbakkOct 16, 2024
  26. Taylor BlauOct 16, 2024
  27. 5/6 doc: update-ref: discuss symbolic linkskristofferhaugsbakk@fastmail.com, Oct 15, 2024
  28. Kristoffer HaugsbakkOct 15, 2024
  29. Taylor BlauOct 16, 2024
  30. 6/6 doc: mutually link update-ref and symbolic-refkristofferhaugsbakk@fastmail.com, Oct 15, 2024
  31. Bence FerdinandyOct 16, 2024
  32. Taylor BlauOct 16, 2024
  33. Kristoffer HaugsbakkOct 16, 2024
  34. 0/6 doc: update-ref: amend old material and discuss symrefskristofferhaugsbakk@fastmail.com, Oct 19, 2024
  35. 1/6 Documentation/git-update-ref.txt: drop “flag”kristofferhaugsbakk@fastmail.com, Oct 19, 2024
  36. karthik nayakOct 20, 2024
  37. 2/6 Documentation/git-update-ref.txt: remove safety paragraphskristofferhaugsbakk@fastmail.com, Oct 19, 2024
  38. karthik nayakOct 20, 2024
  39. Kristoffer HaugsbakkOct 20, 2024
  40. Kristoffer HaugsbakkOct 20, 2024
  41. 3/6 Documentation/git-update-ref.txt: demote symlink to last sectionkristofferhaugsbakk@fastmail.com, Oct 19, 2024
  42. 4/6 Documentation/git-update-ref.txt: remove confusing paragraphkristofferhaugsbakk@fastmail.com, Oct 19, 2024
  43. 5/6 Documentation/git-update-ref.txt: discuss symbolic refskristofferhaugsbakk@fastmail.com, Oct 19, 2024
  44. 6/6 Documentation: mutually link update-ref and symbolic-refkristofferhaugsbakk@fastmail.com, Oct 19, 2024
  45. karthik nayakOct 20, 2024
  46. 0/6 doc: update-ref: amend old material and discuss symrefskristofferhaugsbakk@fastmail.com, Oct 21, 2024
  47. 1/6 Documentation/git-update-ref.txt: drop “flag”kristofferhaugsbakk@fastmail.com, Oct 21, 2024
  48. 2/6 Documentation/git-update-ref.txt: remove safety paragraphskristofferhaugsbakk@fastmail.com, Oct 21, 2024
  49. 3/6 Documentation/git-update-ref.txt: demote symlink to last sectionkristofferhaugsbakk@fastmail.com, Oct 21, 2024
  50. 4/6 Documentation/git-update-ref.txt: remove confusing paragraphkristofferhaugsbakk@fastmail.com, Oct 21, 2024
  51. 5/6 Documentation/git-update-ref.txt: discuss symbolic refskristofferhaugsbakk@fastmail.com, Oct 21, 2024
  52. 6/6 Documentation: mutually link update-ref and symbolic-refkristofferhaugsbakk@fastmail.com, Oct 21, 2024
  53. Taylor BlauOct 21, 2024
  54. Andreas SchwabOct 12, 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.