git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 3/3] Group common commands into for groups for easier navigation

From
pclouds@gmail.com <pclouds@gmail.com>
Date
Dec 1, 2006, 15:08 UTC
Message-ID
<11649857351377-git-send-email-pclouds@gmail.com>
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
Previous: pclouds@gmail.com
Message 2 of 2 in “Prepare for grouped common command list generation”
  1. 2/3 Prepare for grouped common command list generationpclouds@gmail.com, Dec 1, 2006
  2. 3/3 Group common commands into for groups for easier navigationpclouds@gmail.com, Dec 1, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.