From: pclouds@gmail.com
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 3/3] Group common commands into for groups for easier navigation
Date: Fri, 1 Dec 2006 22:08:31 +0700 [thread overview]
Message-ID: <11649857351377-git-send-email-pclouds@gmail.com> (raw)
In-Reply-To: <11649857203869-git-send-email-pclouds@gmail.com>
Repository/Branch level commands are grouped into group Repository
File manipulation commands are in group Manipulation
Other status commands are in group Status
The rest is in group Other
Signed-off-by: Nguyá»
n Thái Ngá»c Duy <pclouds@gmail.com>
---
This is a suggestion. Someone may have better layout than me.
generate-cmdlist.sh | 35 +++++++++++++++++++++--------------
1 files changed, 21 insertions(+), 14 deletions(-)
diff --git a/generate-cmdlist.sh b/generate-cmdlist.sh
index b45495d..f385854 100755
--- a/generate-cmdlist.sh
+++ b/generate-cmdlist.sh
@@ -10,33 +10,40 @@ struct cmdname_help
struct cmdname_help common_cmds[] = {"
cat <<\EOF |
-add
-apply
-archive
-bisect
+G:Repository
+init-db
branch
-checkout
-cherry-pick
clone
-commit
-diff
fetch
-grep
-init-db
-log
merge
-mv
prune
pull
push
-rebase
reset
+tag
+
+G:Manipulation
+add
+apply
+checkout
+commit
+mv
revert
rm
+
+G:Status
+diff
+log
show
show-branch
status
-tag
+
+G:Other
+archive
+bisect
+cherry-pick
+grep
+rebase
verify-tag
EOF
while read cmd
--
1.4.4.rc1.g9124
prev parent reply other threads:[~2006-12-01 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1164985711791-git-send-email-pclouds@gmail.com>
2006-12-01 15:08 ` [PATCH 2/3] Prepare for grouped common command list generation pclouds
2006-12-01 15:08 ` pclouds [this message]
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=11649857351377-git-send-email-pclouds@gmail.com \
--to=pclouds@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).