git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Wes Lord via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Wes Lord <weslord@gmail.com>
Subject: Re: [PATCH] new-command.txt: update reference to builtin docs
Date: Mon, 06 Feb 2023 14:07:17 -0800	[thread overview]
Message-ID: <xmqqo7q64fe2.fsf@gitster.g> (raw)
In-Reply-To: <pull.1451.git.git.1675477659972.gitgitgadget@gmail.com> (Wes Lord via GitGitGadget's message of "Sat, 04 Feb 2023 02:27:39 +0000")

"Wes Lord via GitGitGadget" <gitgitgadget@gmail.com> writes:

> 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

I was sort of hoping that this document has outlived its usefulness
and been taken over by more recently written guies, but it does not
appear to be the case.  A more recently written MyFirstContribution
references this, so keeping its contents fresh does have value.

Thanks, will queue.

> 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

      reply	other threads:[~2023-02-06 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04  2:27 [PATCH] new-command.txt: update reference to builtin docs Wes Lord via GitGitGadget
2023-02-06 22:07 ` Junio C Hamano [this message]

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=xmqqo7q64fe2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --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 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).