From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] git: add missing usages for subcommands
Date: Sun, 01 Oct 2023 08:49:35 -0700 [thread overview]
Message-ID: <96670F28F4330D15582F2FEA03722ACF@smtp.pobox.com> (raw)
In-Reply-To: <1427BD937CD79DC163DBD72D08F63946@eigenstate.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?
2) I didn't include git/hist in the doc patch: that's a "shouldn't
need to use" program as well?
>
> Quoth Romano <unobe@cpan.org>:
> > ---
> > diff db2177614df64fa9ccf3dae30cdf24df1ce0a0be 405b4e7cff97415ef62ed448de0eb33f981a8333
> > --- a/sys/man/1/git
> > +++ b/sys/man/1/git
> > @@ -71,6 +71,25 @@
> > .I commits...
> > ]
> > .PP
> > +.B git/get
> > +[
> > +.B -dl
> > +]
> > +[
> > +.B -b
> > +.I branch
> > +]
> > +[
> > +.B -u
> > +.I upstream
> > +]
> > +.I remote
> > +.PP
> > +.B git/fs
> > +[
> > +.B -d
> > +]
> > +.PP
> > .B git/import
> > [
> > .B -n
> > @@ -152,6 +171,11 @@
> > ]
> > .I query
> > .PP
> > +.B git/repack
> > +[
> > +.B -d
> > +]
> > +.PP
> > .B git/revert
> > [
> > .B -c
> > @@ -161,6 +185,61 @@
> > .PP
> > .B git/rm
> > .I path...
> > +.PP
> > +.B git/save
> > +.B -n
> > +.I name
> > +.B -e
> > +.I email
> > +.B -m
> > +.I message
> > +.B -d
> > +.I date
> > +[
> > +.B -N
> > +.I committer-name
> > +.B -E
> > +.I committer-email
> > +]
> > +[
> > +.B -p
> > +.I parent1
> > +[
> > +.B -p
> > +.I parent2
> > +]
> > +…
> > +]
> > +[
> > +.I files…
> > +]
> > +.PP
> > +.B git/send
> > +[
> > +.B -adf
> > +]
> > +[
> > +.B -b
> > +.I branch1
> > +[
> > +.B -b
> > +.I branch2
> > +]
> > +…
> > +]
> > +[
> > +.B -r
> > +.I branch1
> > +[
> > +.B -r
> > +.I branch2
> > +]
> > +…
> > +]
> > +.I remote
> > +[
> > +.I reponame
> > +]
> > .PP
> > .B git/serve
> > [
> >
>
next prev parent reply other threads:[~2023-10-01 15:54 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 [this message]
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
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=96670F28F4330D15582F2FEA03722ACF@smtp.pobox.com \
--to=unobe@cpan.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).