From: Kristoffer Haugsbakk <code@xxxxxxxxxxxxxxx>
This paragraph interrupts the flow of this section by going into detail
about what a symbolic ref file is and how it is implemented. It is not
clear what the purpose is since symbolic refs were already mentioned
prior (“possibly dereferencing the symbolic refs”). Worse, it can
confuse the reader about what argument can be a symbolic ref since it
just says “it” and not which of the parameters; in turn the reader can
be lead to try `<new-oid>` and then get a confusing error since
update-ref will just say that it is not a valid SHA1.
Reported-by: Bence Ferdinandy <bence@xxxxxxxxxxxxxx>
Signed-off-by: Kristoffer Haugsbakk <code@xxxxxxxxxxxxxxx>
---
Notes (series):
This paragraph is also from the initial documentation: 129056370ab (Add
missing documentation., 2005-10-04).
Documentation/git-update-ref.txt | 4 ----
1 file changed, 4 deletions(-)
diff --git a/Documentation/git-update-ref.txt b/Documentation/git-update-ref.txt
index c03e65404e8..4bb3389cc7c 100644
--- a/Documentation/git-update-ref.txt
+++ b/Documentation/git-update-ref.txt
@@ -25,10 +25,6 @@ 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.
-It also allows a "ref" file to be a symbolic pointer to another
-ref file by starting with the four-byte header sequence of
-"ref:".
-
If --no-deref is given, <ref> itself is overwritten, rather than
the result of following the symbolic pointers.
--
2.46.1.641.g54e7913fcb6
