From: Junio C Hamano <gitster@pobox•com>
To: "Sébastien Guimmara" <sebastien.guimmara@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH v2 1/3] git help: group common commands by theme
Date: Sat, 02 May 2015 19:23:40 -0700 [thread overview]
Message-ID: <xmqqk2wqwg9f.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <554405D5.9080702@gmail.com> ("Sébastien Guimmara"'s message of "Sat, 02 May 2015 01:01:41 +0200")
Sébastien Guimmara <sebastien.guimmara@gmail•com> writes:
> Finally, list_common_cmds_help() prints those common commands by
> groups, skipping a line between each group:
>
> [...]
>
> The most commonly used git commands are:
> clone Clone a repository into a new directory
> init Create an empty Git repository or reinitialize an existing one
>
> log Show commit logs
> show Show various types of objects
> status Show the working tree status
>
> add Add file contents to the index
> mv Move or rename a file, a directory, or a symlink
> reset Reset current HEAD to the specified state
> rm Remove files from the working tree and from the index
>
> fetch Download objects and refs from another repository
> pull Fetch from and integrate with another repository or a local branch
> push Update remote refs along with associated objects
>
> commit Record changes to the repository
> diff Show changes between commits, commit and working tree, etc
> rebase Forward-port local commits to the updated upstream head
> tag Create, list, delete or verify a tag object signed with GPG
What is the target audience? Are they expected to be familiar
enough with Git that they can guess what the above grouping is based
on without a group header?
I consider myself experienced enough with Git but cannot explain or
justify the placement of "diff" in the above list myself, for
example. I'd say
* starting a working area (clone, init)
* examining the history and state (log, show, status, diff)
* working on the current change (add, checkout, reset)
* growing, marking and tweaking your history (commit, tag, rebase)
* working with others (fetch, pull, push)
might be a more sensible presentation order (and classification).
next prev parent reply other threads:[~2015-05-03 2:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 23:01 [PATCH v2 1/3] git help: group common commands by theme Sébastien Guimmara
2015-05-01 23:06 ` [PATCH v2 2/3] " Sébastien Guimmara
2015-05-02 6:32 ` Luke Diamand
2015-05-02 11:09 ` Sébastien Guimmara
2015-05-02 11:43 ` Andreas Schwab
2015-05-02 11:52 ` Sébastien Guimmara
2015-05-02 14:18 ` Sébastien Guimmara
2015-05-01 23:12 ` [PATCH v2 3/3] " Sébastien Guimmara
2015-05-03 0:19 ` [PATCH v3 0/4] git help: group common commands by themes Sébastien Guimmara
2015-05-03 0:21 ` [PATCH v3 1/4] command-list.txt: " Sébastien Guimmara
2015-05-03 0:22 ` [PATCH v3 2/4] generate-cmdlist.sh: parse common command groups Sébastien Guimmara
2015-05-03 17:55 ` Junio C Hamano
2015-05-03 20:40 ` Eric Sunshine
2015-05-03 20:53 ` Sébastien Guimmara
2015-05-03 21:10 ` Eric Sunshine
2015-05-03 19:18 ` Eric Sunshine
2015-05-03 20:10 ` Eric Sunshine
2015-05-03 0:23 ` [PATCH v3 3/4] help.c - group common commands by theme Sébastien Guimmara
2015-05-03 19:44 ` Eric Sunshine
2015-05-03 0:24 ` [PATCH v3 4/4] api-builtin.txt: explain common command groups Sébastien Guimmara
2015-05-03 20:02 ` Eric Sunshine
2015-05-03 20:59 ` Sébastien Guimmara
2015-05-03 21:13 ` Eric Sunshine
[not found] ` <CAHYJk3S3s4RjFMUaomP2wUVBbcTLRGYrAOa-uDjrfsKqUuWPog@mail.gmail.com>
2015-05-03 22:32 ` Sébastien Guimmara
2015-05-03 2:23 ` Junio C Hamano [this message]
2015-05-03 13:54 ` [PATCH v2 1/3] git help: group common commands by theme Sébastien Guimmara
2015-05-03 13:57 ` Sébastien Guimmara
2015-05-03 17:16 ` Junio C Hamano
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=xmqqk2wqwg9f.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sebastien.guimmara@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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