From: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>
To: git@vger.kernel.org
Cc: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>
Subject: [PATCH v5 0/6] git help: group common commands by theme
Date: Sat, 9 May 2015 19:17:30 +0200 [thread overview]
Message-ID: <1431191856-10949-1-git-send-email-sebastien.guimmara@gmail.com> (raw)
This v5 includes suggestions from Junio C Hamano, Eric Sunshine and
Emma Jane Hogbin Westby, as well as a complete and much cleaner rewrite
of the generate-cmdlist parser in awk by Eric Sunshine.
The main idea of this version is to go a little further in the idea of
making 'git help' a warmer welcome to the unfamiliar user, by a gentle
summary of the typical Git workflow. Instead of simply telling what
the Git common commands are, we rather explain how they fit in the
typical workflow, ordered in (chrono)logical order:
1. I setup my repo (init)
2. I work on changes (worktree)
3. I gather information on the history (info)
4. I grow, tweak and clean my local history (history)
5. To finally share my nice contribution with the world (remote)
Sébastien Guimmara (6):
generate-cmdlist: parse common group commands
help.c: output the typical Git workflow
command-list.txt: group common commands by theme
Makefile: update to new command-list.txt format
new-command.txt: mention the common command groups
cmd-list.perl: ignore all lines until [commands]
Documentation/cmd-list.perl | 8 +++++-
Documentation/howto/new-command.txt | 4 ++-
Makefile | 8 +++---
command-list.txt | 56 ++++++++++++++++++++++---------------
generate-cmdlist.awk | 38 +++++++++++++++++++++++++
help.c | 25 +++++++++++++++--
6 files changed, 109 insertions(+), 30 deletions(-)
create mode 100644 generate-cmdlist.awk
--
2.4.0
next reply other threads:[~2015-05-09 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 17:17 Sébastien Guimmara [this message]
2015-05-09 17:17 ` [PATCH v5 1/6] generate-cmdlist: parse common group commands Sébastien Guimmara
2015-05-11 6:12 ` Eric Sunshine
2015-05-09 17:17 ` [PATCH v5 2/6] help.c: output the typical Git workflow Sébastien Guimmara
2015-05-11 6:24 ` Eric Sunshine
2015-05-09 17:17 ` [PATCH v5 3/6] command-list.txt: group common commands by theme Sébastien Guimmara
2015-05-11 6:20 ` Eric Sunshine
2015-05-09 17:17 ` [PATCH v5 4/6] Makefile: update to new command-list.txt format Sébastien Guimmara
2015-05-11 6:44 ` Eric Sunshine
2015-05-09 17:17 ` [PATCH v5 5/6] new-command.txt: mention the common command groups Sébastien Guimmara
2015-05-11 6:47 ` Eric Sunshine
2015-05-09 17:17 ` [PATCH v5 6/6] cmd-list.perl: ignore all lines until [commands] Sébastien Guimmara
2015-05-11 6:59 ` Eric Sunshine
2015-05-11 5:52 ` [PATCH v5 0/6] git help: group common commands by theme Eric Sunshine
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=1431191856-10949-1-git-send-email-sebastien.guimmara@gmail.com \
--to=sebastien.guimmara@gmail.com \
--cc=git@vger.kernel.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).