From: "Wes Lord via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Wes Lord <weslord@gmail.com>, Wes Lord <weslord@gmail.com>
Subject: [PATCH] new-command.txt: update reference to builtin docs
Date: Sat, 04 Feb 2023 02:27:39 +0000 [thread overview]
Message-ID: <pull.1451.git.git.1675477659972.gitgitgadget@gmail.com> (raw)
From: Wes Lord <weslord@gmail.com>
Commit ec14d4ecb5 (builtin.h: take over documentation from
api-builtin.txt, 2017-08-02) deleted api-builtin.txt and moved the
contents into builtin.h, but new-command.txt still references the old
file.
Signed-off-by: Wes Lord <weslord@gmail.com>
---
new-command.txt: update reference to builtin docs
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1451%2Fweslord%2Fdoc-builtin-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1451/weslord/doc-builtin-v1
Pull-Request: https://github.com/git/git/pull/1451
Documentation/howto/new-command.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt
index 15a4c8031f1..880c51112ba 100644
--- a/Documentation/howto/new-command.txt
+++ b/Documentation/howto/new-command.txt
@@ -1,13 +1,13 @@
From: Eric S. Raymond <esr@thyrsus.com>
Abstract: This is how-to documentation for people who want to add extension
- commands to Git. It should be read alongside api-builtin.txt.
+ commands to Git. It should be read alongside builtin.h.
Content-type: text/asciidoc
How to integrate new subcommands
================================
This is how-to documentation for people who want to add extension
-commands to Git. It should be read alongside api-builtin.txt.
+commands to Git. It should be read alongside builtin.h.
Runtime environment
-------------------
base-commit: 2fc9e9ca3c7505bc60069f11e7ef09b1aeeee473
--
gitgitgadget
next reply other threads:[~2023-02-04 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 2:27 Wes Lord via GitGitGadget [this message]
2023-02-06 22:07 ` [PATCH] new-command.txt: update reference to builtin docs 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.1451.git.git.1675477659972.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=weslord@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.