9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] git: add missing usages for subcommands
Date: Sun, 01 Oct 2023 12:42:35 -0400	[thread overview]
Message-ID: <D9543B955541EE3E81A5728709F8DF67@eigenstate.org> (raw)
In-Reply-To: <96670F28F4330D15582F2FEA03722ACF@smtp.pobox.com>

Quoth unobe@cpan.org:
> Quoth ori@eigenstate.org:
> > these were intentionally ommitted; you shouldn't need to use
> > them. They exist for scripts like 'git/commit', 'git/push', and
> > 'git/pull'.
> 
> Thanks, Ori.  I didn't realize that programs existing in the
> distribution shouldn't be documented.
>
> Two follow-ups:
> 
> 1) Is that something that is standard and I've just never realized it?

Not sure about 'standard'; it's a judgement call.

I wouldn't mind having some form of documentation, but
putting them in the main git manpage just confuses the
user on how to do things, IMO.

It's the same reason that debug flags are typically not
documented; if you're interacting with them, you're
typically already in the code.

> 2) I didn't include git/hist in the doc patch: that's a "shouldn't
>    need to use" program as well?

No, that's one that's quite useful; it's basically
git blame on a budget (because it's honesty a pain
in the ass to implement 'blame'.


  reply	other threads:[~2023-10-01 16:45 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 [this message]
2023-10-01 20:14       ` ori
2023-10-01 23:34       ` unobe
2023-10-02  3:40         ` Kurt H Maier

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=D9543B955541EE3E81A5728709F8DF67@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).