From: pclouds@gmail.com
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 2/3] Prepare for grouped common command list generation
Date: Fri, 1 Dec 2006 22:08:30 +0700 [thread overview]
Message-ID: <11649857203869-git-send-email-pclouds@gmail.com> (raw)
In-Reply-To: <1164985711791-git-send-email-pclouds@gmail.com>
Signed-off-by: Nguyá»
n Thái Ngá»c Duy <pclouds@gmail.com>
---
generate-cmdlist.sh | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/generate-cmdlist.sh b/generate-cmdlist.sh
index 5450918..b45495d 100755
--- a/generate-cmdlist.sh
+++ b/generate-cmdlist.sh
@@ -9,7 +9,7 @@ struct cmdname_help
struct cmdname_help common_cmds[] = {"
-sort <<\EOF |
+cat <<\EOF |
add
apply
archive
@@ -41,6 +41,11 @@ verify-tag
EOF
while read cmd
do
+ [ -z "$cmd" ] && continue
+ if echo $cmd|grep -q '^G:'; then
+ echo ' {"'$(echo -n $cmd|sed 's/^G://')'",""},'
+ continue
+ fi
sed -n '
/NAME/,/git-'"$cmd"'/H
${
--
1.4.4.rc1.g9124
next 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 ` pclouds [this message]
2006-12-01 15:08 ` [PATCH 3/3] Group common commands into for groups for easier navigation pclouds
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=11649857203869-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.