Re: [9front] [PATCH] git: add missing usages for subcommands

[ori@eigenstate.org]

Quoth ori@eigenstate.org:
> 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'.
> 

git/repack may also make sense to document; it's kind
of rarely needed maintenance, but it *may* make sense
for users to use -- though it's just as much a test
program for the pack generation logic.