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

[PATCH 0/2] improve documentation around git-update-ref

From
Karthik Nayak <karthik.188@gmail.com>
Date
Apr 1, 2024, 14:45 UTC
Message-ID
<20240401144542.88027-1-knayak@gitlab.com>
From: Karthik Nayak <karthik.188@gmail.com>

This patch series was derived out of the discussion [1] around my other patch series to add symref support for `git-update-ref(1)` [2].

The aim of these patches is to improve clarity around OIDs in the documentation. This makes it easier to draw parallels between regular ref updates and symref updates. The symref patch series will be rebased on top of this in the upcoming version.

[1]: https://public-inbox.org/git/20240330224623.579457-1-knayak@gitlab.com/T/#m7bb4d1f44b656d7cfb73ed3220b990aa6d1ac247 [2]: https://public-inbox.org/git/20240330224623.579457-1-knayak@gitlab.com/T/#t

Karthik Nayak (2):
  update-ref: use {old,new}-oid instead of {old,new}value
  githooks: use {old,new}-oid instead of {old,new}-value
 Documentation/git-update-ref.txt | 58 ++++++++++++++++----------------
 Documentation/githooks.txt       | 16 ++++-----
 builtin/update-ref.c             | 26 +++++++-------
 3 files changed, 50 insertions(+), 50 deletions(-)
-- 
2.43.GIT
Next: Karthik Nayak
Message 1 of 11 in “improve documentation around git-update-ref”
  1. 0/2 improve documentation around git-update-refKarthik Nayak, Apr 1, 2024
  2. 1/2 update-ref: use {old,new}-oid instead of {old,new}valueKarthik Nayak, Apr 1, 2024
  3. Junio C HamanoApr 1, 2024
  4. Karthik NayakApr 1, 2024
  5. Junio C HamanoApr 1, 2024
  6. Karthik NayakApr 2, 2024
  7. 2/2 githooks: use {old,new}-oid instead of {old,new}-valueKarthik Nayak, Apr 1, 2024
  8. 0/2 improve documentation around git-update-refKarthik Nayak, Apr 2, 2024
  9. 2/2 githooks: use {old,new}-oid instead of {old,new}-valueKarthik Nayak, Apr 2, 2024
  10. 1/2 update-ref: use {old,new}-oid instead of {old,new}valueKarthik Nayak, Apr 2, 2024
  11. Patrick SteinhardtApr 2, 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.