git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Third try at documenting command integration requirements.

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 26, 2012, 21:41 UTC
Message-ID
<7v624sqbxo.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20121126053557.E56434065F@snark.thyrsus.com>
esr@thyrsus.com (Eric S. Raymond) writes:
Show 9 quoted lines
> @@ -0,0 +1,91 @@
> += Integrating 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.
> +
> +== Runtime environment ==
> +
> +git subcommands are standalone executables that live in the git

Even though "={n} title ={n}" is a valid AsciiDoc heading, all other files use (older) underscored titles; please refrain from being original.

Especially, this interferes with the way the api-index.txt file in the same directory is autogenerated.

Previous: Eric S. RaymondNext: Eric S. Raymond
Message 9 of 10 in “Third try at documenting command integration requirements.”
  1. Third try at documenting command integration requirements.Eric S. Raymond, Nov 26, 2012
  2. Perry HutchisonNov 26, 2012
  3. Junio C HamanoNov 26, 2012
  4. Eric S. RaymondNov 26, 2012
  5. Michael HaggertyNov 27, 2012
  6. Eric S. RaymondNov 27, 2012
  7. Junio C HamanoNov 28, 2012
  8. Eric S. RaymondNov 28, 2012
  9. Junio C HamanoNov 26, 2012
  10. Eric S. RaymondNov 26, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.