From: "Jouke Witteveen via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jouke Witteveen <j.witteveen@gmail.com>,
Jouke Witteveen <j.witteveen@gmail.com>
Subject: [PATCH] doc: update references to renamed AsciiDoc files
Date: Wed, 21 May 2025 19:05:10 +0000 [thread overview]
Message-ID: <pull.1971.git.git.1747854310479.gitgitgadget@gmail.com> (raw)
From: Jouke Witteveen <j.witteveen@gmail.com>
The .txt extensions were changed to .adoc in 1f010d6 (doc: use .adoc
extension for AsciiDoc files, 2025-01-20). References to the renamed
files were not updated yet.
Signed-off-by: Jouke Witteveen <j.witteveen@gmail.com>
---
doc: update references to renamed AsciiDoc files
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1971%2Fjoukewitteveen%2Frenamed-files-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1971/joukewitteveen/renamed-files-v1
Pull-Request: https://github.com/git/git/pull/1971
Documentation/gitprotocol-v2.adoc | 4 ++--
Documentation/technical/build-systems.adoc | 2 +-
contrib/subtree/README | 2 +-
mergetools/vimdiff | 4 ++--
sub-process.h | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/gitprotocol-v2.adoc b/Documentation/gitprotocol-v2.adoc
index 5598c93e67c3..abc42efcc774 100644
--- a/Documentation/gitprotocol-v2.adoc
+++ b/Documentation/gitprotocol-v2.adoc
@@ -54,7 +54,7 @@ In general a client can request to speak protocol v2 by sending
`version=2` through the respective side-channel for the transport being
used which inevitably sets `GIT_PROTOCOL`. More information can be
found in linkgit:gitprotocol-pack[5] and linkgit:gitprotocol-http[5], as well as the
-`GIT_PROTOCOL` definition in `git.txt`. In all cases the
+`GIT_PROTOCOL` definition in `git.adoc`. In all cases the
response from the server is the capability advertisement.
Git Transport
@@ -99,7 +99,7 @@ Uses the `--http-backend-info-refs` option to
linkgit:git-upload-pack[1].
The server may need to be configured to pass this header's contents via
-the `GIT_PROTOCOL` variable. See the discussion in `git-http-backend.txt`.
+the `GIT_PROTOCOL` variable. See the discussion in `git-http-backend.adoc`.
Capability Advertisement
------------------------
diff --git a/Documentation/technical/build-systems.adoc b/Documentation/technical/build-systems.adoc
index d9dafb407c40..1ae2a5292f3b 100644
--- a/Documentation/technical/build-systems.adoc
+++ b/Documentation/technical/build-systems.adoc
@@ -32,7 +32,7 @@ that generally have somebody running test pipelines against regularly:
- OpenBSD
The platforms which must be supported by the tool should be aligned with our
-[platform support policy](platform-support.txt).
+xref:platform-support.adoc[platform support policy].
=== Auto-detection of supported features
diff --git a/contrib/subtree/README b/contrib/subtree/README
index c686b4a69b12..65d167b678c8 100644
--- a/contrib/subtree/README
+++ b/contrib/subtree/README
@@ -1,5 +1,5 @@
-Please read git-subtree.txt for documentation.
+Please read git-subtree.adoc for documentation.
Please don't contact me using github mail; it's slow, ugly, and worst of
all, redundant. Email me instead at apenwarr@gmail.com and I'll be happy to
diff --git a/mergetools/vimdiff b/mergetools/vimdiff
index ffc9be86c83d..8fca3a2a2fda 100644
--- a/mergetools/vimdiff
+++ b/mergetools/vimdiff
@@ -274,8 +274,8 @@ gen_cmd () {
# definition.
#
# The syntax of the "layout definitions" is explained in "Documentation/
- # mergetools/vimdiff.txt" but you can already intuitively understand how
- # it works by knowing that...
+ # mergetools/vimdiff.adoc" but you can already intuitively understand
+ # how it works by knowing that...
#
# * "+" means "a new vim tab"
# * "/" means "a new vim horizontal split"
diff --git a/sub-process.h b/sub-process.h
index 6a61638a8ace..bfc3959a1b48 100644
--- a/sub-process.h
+++ b/sub-process.h
@@ -73,7 +73,7 @@ static inline struct child_process *subprocess_get_child_process(
/*
* Perform the version and capability negotiation as described in the
- * "Handshake" section of long-running-process-protocol.txt using the
+ * "Handshake" section of long-running-process-protocol.adoc using the
* given requested versions and capabilities. The "versions" and "capabilities"
* parameters are arrays terminated by a 0 or blank struct.
*
base-commit: d50a5e8939abfc07c2ff97ae72e9330939b36ee0
--
gitgitgadget
next reply other threads:[~2025-05-21 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 19:05 Jouke Witteveen via GitGitGadget [this message]
2025-05-21 19:33 ` [PATCH] doc: update references to renamed AsciiDoc files Junio C Hamano
2025-05-22 9:23 ` Jouke Witteveen
2025-05-22 16:12 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1971.git.git.1747854310479.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.witteveen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).