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

[PATCH v2 2/2] githooks: use {old,new}-oid instead of {old,new}-value

From
Karthik Nayak <karthik.188@gmail.com>
Date
Apr 2, 2024, 06:49 UTC
Message-ID
<20240402064915.191104-3-knayak@gitlab.com>
In-Reply-To
<20240402064915.191104-1-knayak@gitlab.com>
From: Karthik Nayak <karthik.188@gmail.com>

Similar to the previous commit, rename {old,new}-value in the 'githooks' documentation to {old,new}-oid. This improves clarity and also ensures consistency within the document.

Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
---
 Documentation/githooks.txt | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt
index 37f91d5b50..ee9b92c90d 100644
--- a/Documentation/githooks.txt
+++ b/Documentation/githooks.txt
@@ -275,12 +275,12 @@ This hook executes once for the receive operation. It takes no
 arguments, but for each ref to be updated it receives on standard
 input a line of the format:
 
-  <old-value> SP <new-value> SP <ref-name> LF
+  <old-oid> SP <new-oid> SP <ref-name> LF
 
-where `<old-value>` is the old object name stored in the ref,
-`<new-value>` is the new object name to be stored in the ref and
+where `<old-oid>` is the old object name stored in the ref,
+`<new-oid>` is the new object name to be stored in the ref and
 `<ref-name>` is the full name of the ref.
-When creating a new ref, `<old-value>` is the all-zeroes object name.
+When creating a new ref, `<old-oid>` is the all-zeroes object name.
 
 If the hook exits with non-zero status, none of the refs will be
 updated. If the hook exits with zero, updating of individual refs can
@@ -503,13 +503,13 @@ given reference transaction is in:
 For each reference update that was added to the transaction, the hook
 receives on standard input a line of the format:
 
-  <old-value> SP <new-value> SP <ref-name> LF
+  <old-oid> SP <new-oid> SP <ref-name> LF
 
-where `<old-value>` is the old object name passed into the reference
-transaction, `<new-value>` is the new object name to be stored in the
+where `<old-oid>` is the old object name passed into the reference
+transaction, `<new-oid>` is the new object name to be stored in the
 ref and `<ref-name>` is the full name of the ref. When force updating
 the reference regardless of its current value or when the reference is
-to be created anew, `<old-value>` is the all-zeroes object name. To
+to be created anew, `<old-oid>` is the all-zeroes object name. To
 distinguish these cases, you can inspect the current value of
 `<ref-name>` via `git rev-parse`.
 
-- 
2.43.GIT
Previous: Karthik NayakNext: Karthik Nayak
Message 9 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.