doc: prepare for a world without whatchanged
Some documentation examples reference "whatchanged", either as a placeholder command or an example of source structure. To reduce the need for future edits when `whatchanged` is removed, replace these references with alternatives: - In `MyFirstObjectWalk.adoc`, use `version` as the nearby anchor point for `walken`, instead of `whatchanged`. - In `user-manual.adoc`, cite `show` instead of `whatchanged` as a command whose source lives in the same file as `log`. Helped-by: Elijah Newren <newren@gmail.com> [en: log message] Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
May 12, 2025 at 12:03 UTC
ba69a6c66d6b349f730bdb3b9e44c3b49dd53e91
2 files changed
+3
-3
Documentation/MyFirstObjectWalk.adoc
+2
-2
@@ -83,13 +83,13 @@ int cmd_walken(int argc, const char **argv, const char *prefix)
83
}
84
----
85
86
-Also add the relevant line in `builtin.h` near `cmd_whatchanged()`:
86
+Also add the relevant line in `builtin.h` near `cmd_version()`:
87
88
----
89
int cmd_walken(int argc, const char **argv, const char *prefix);
90
----
91
92
-Include the command in `git.c` in `commands[]` near the entry for `whatchanged`,
92
+Include the command in `git.c` in `commands[]` near the entry for `version`,
93
maintaining alphabetical ordering:
94
95
----
Documentation/user-manual.adoc
+1
-1
@@ -4240,7 +4240,7 @@ command `git`. The source side of a builtin is
4240
- an entry in `BUILTIN_OBJECTS` in the `Makefile`.
4241
4242
Sometimes, more than one builtin is contained in one source file. For
4243
-example, `cmd_whatchanged()` and `cmd_log()` both reside in `builtin/log.c`,
4243
+example, `cmd_show()` and `cmd_log()` both reside in `builtin/log.c`,
4244
since they share quite a bit of code. In that case, the commands which are
4245
_not_ named like the `.c` file in which they live have to be listed in
4246
`BUILT_INS` in the `Makefile`.