From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: [PATCH] submodule: make 'show' an alias for 'summary'
Date: Sat, 29 Sep 2012 19:13:14 +0530 [thread overview]
Message-ID: <1348926195-4788-1-git-send-email-artagnon@gmail.com> (raw)
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
Like 'git remote show', 'git stash show'.
Documentation/git-submodule.txt | 3 ++-
git-submodule.sh | 9 ++++++++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
index fbbbcb2..498bb5c 100644
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -15,7 +15,7 @@ SYNOPSIS
'git submodule' [--quiet] init [--] [<path>...]
'git submodule' [--quiet] update [--init] [-N|--no-fetch] [--rebase]
[--reference <repository>] [--merge] [--recursive] [--] [<path>...]
-'git submodule' [--quiet] summary [--cached|--files] [(-n|--summary-limit) <n>]
+'git submodule' [--quiet] summary|show [--cached|--files] [(-n|--summary-limit) <n>]
[commit] [--] [<path>...]
'git submodule' [--quiet] foreach [--recursive] <command>
'git submodule' [--quiet] sync [--] [<path>...]
@@ -151,6 +151,7 @@ If `--recursive` is specified, this command will recurse into the
registered submodules, and update any nested submodules within.
summary::
+show::
Show commit summary between the given commit (defaults to HEAD) and
working tree/index. For a submodule in question, a series of commits
in the submodule between the given super project commit and the
diff --git a/git-submodule.sh b/git-submodule.sh
index 9210f3a..1d61ebd 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -889,6 +889,13 @@ cmd_summary() {
fi
}
#
+# Alias for cmd_summary
+#
+cmd_show()
+{
+ cmd_summary "$@"
+}
+#
# List all submodules, prefixed with:
# - submodule not initialized
# + different revision checked out
@@ -1049,7 +1056,7 @@ cmd_sync()
while test $# != 0 && test -z "$command"
do
case "$1" in
- add | foreach | init | update | status | summary | sync)
+ add | foreach | init | update | status | summary | show | sync)
command=$1
;;
-q|--quiet)
--
1.7.10.4
next reply other threads:[~2012-09-29 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 13:43 Ramkumar Ramachandra [this message]
2012-09-29 13:43 ` [PATCH] submodule: use abbreviated sha1 in 'status' output Ramkumar Ramachandra
2012-09-29 14:31 ` Jens Lehmann
2012-09-29 14:45 ` Ramkumar Ramachandra
2012-09-29 15:05 ` Jens Lehmann
2012-10-01 6:42 ` Ramkumar Ramachandra
2012-10-01 17:22 ` Jens Lehmann
2012-09-29 14:49 ` [PATCH] submodule: make 'show' an alias for 'summary' Jens Lehmann
2012-09-29 15:07 ` Ramkumar Ramachandra
2012-09-29 15:27 ` Jens Lehmann
2012-10-01 6:45 ` Ramkumar Ramachandra
2012-10-01 17:26 ` Jens Lehmann
2012-10-01 17:33 ` Ramkumar Ramachandra
2012-10-01 19:31 ` Jens Lehmann
2012-10-01 17:41 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1348926195-4788-1-git-send-email-artagnon@gmail.com \
--to=artagnon@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).