From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] git: add missing usages for subcommands
Date: Sun, 1 Oct 2023 20:40:12 -0700 [thread overview]
Message-ID: <ZRo7nDIjFYv3pBK2@wopr> (raw)
In-Reply-To: <A1FA07F302666A10482EAB62ED14EE37@smtp.pobox.com>
On Sun, Oct 01, 2023 at 04:34:00PM -0700, unobe@cpan.org wrote:
>
> What if, in the long-form area that expanded on the different git
> programs, the ones which aren't meant to be used directly are
> mentioned as such? For me, some documentation of all programs is more
> useful than none, even ones meant for internal-use only? Something
> like this at the end:
> "Git/get, git/repack, git/save, and git/send are primarily internal
> commands, and therefore not documented beyond their usage lines above
> and their own code."
the traditional approach is for ori, or an intern, to write a paper
about this git implementation, so it can live in /sys/doc. I assume,
for the sake of argument, that ori has unlimited free time and interns
to accomplish this, and so I look forward to reading the paper when it
is published, for the sake of argument, later today.
khm
prev parent reply other threads:[~2023-10-02 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 6:18 Romano
2023-10-01 14:48 ` ori
2023-10-01 15:49 ` unobe
2023-10-01 16:42 ` ori
2023-10-01 20:14 ` ori
2023-10-01 23:34 ` unobe
2023-10-02 3:40 ` Kurt H Maier [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=ZRo7nDIjFYv3pBK2@wopr \
--to=khm@sciops.net \
--cc=9front@9front.org \
/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).