Skip to content

Commit 5b1967a

Browse files
KarthikNayakgitster
authored andcommitted
githooks: use {old,new}-oid instead of {old,new}-value
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 <[email protected]> Acked-by: Patrick Steinhardt <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 67e943c commit 5b1967a

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

Documentation/githooks.txt

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -275,12 +275,12 @@ This hook executes once for the receive operation. It takes no
275275
arguments, but for each ref to be updated it receives on standard
276276
input a line of the format:
277277

278-
<old-value> SP <new-value> SP <ref-name> LF
278+
<old-oid> SP <new-oid> SP <ref-name> LF
279279

280-
where `<old-value>` is the old object name stored in the ref,
281-
`<new-value>` is the new object name to be stored in the ref and
280+
where `<old-oid>` is the old object name stored in the ref,
281+
`<new-oid>` is the new object name to be stored in the ref and
282282
`<ref-name>` is the full name of the ref.
283-
When creating a new ref, `<old-value>` is the all-zeroes object name.
283+
When creating a new ref, `<old-oid>` is the all-zeroes object name.
284284

285285
If the hook exits with non-zero status, none of the refs will be
286286
updated. If the hook exits with zero, updating of individual refs can
@@ -503,13 +503,13 @@ given reference transaction is in:
503503
For each reference update that was added to the transaction, the hook
504504
receives on standard input a line of the format:
505505

506-
<old-value> SP <new-value> SP <ref-name> LF
506+
<old-oid> SP <new-oid> SP <ref-name> LF
507507

508-
where `<old-value>` is the old object name passed into the reference
509-
transaction, `<new-value>` is the new object name to be stored in the
508+
where `<old-oid>` is the old object name passed into the reference
509+
transaction, `<new-oid>` is the new object name to be stored in the
510510
ref and `<ref-name>` is the full name of the ref. When force updating
511511
the reference regardless of its current value or when the reference is
512-
to be created anew, `<old-value>` is the all-zeroes object name. To
512+
to be created anew, `<old-oid>` is the all-zeroes object name. To
513513
distinguish these cases, you can inspect the current value of
514514
`<ref-name>` via `git rev-parse`.
515515

0 commit comments

Comments
 (0)