From: Ping Yin <pkufranky@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: [PATCH 0/7] git-submodule enhancements
Date: Fri, 14 Mar 2008 01:56:34 +0800 [thread overview]
Message-ID: <1205431001-18590-1-git-send-email-pkufranky@gmail.com> (raw)
This patch series do following enhancements for git-submodule
- Fall back on .gitmodules if info not found in $GIT_DIR/config
- multi-level module definition
- Don't die when command fails for one submodule
with diffstat
git-submodule.sh | 316 +++++++++++++++++++++++++++++++-------------
t/t7400-submodule-basic.sh | 31 ++++-
and commits
git-submodule: Avoid 'fatal: cannot describe' message
git-submodule: Extract functions module_info and module_url
git-submodule: Extract absolute_url & move absolute url logic to module_clone
git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config
git-submodule: Extract module_add from cmd_add
git-submodule: multi-level module definition
git-submodule: Don't die when command fails for one submodule
next reply other threads:[~2008-03-13 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 17:56 Ping Yin [this message]
2008-03-13 17:56 ` [PATCH 1/7] git-submodule: Avoid 'fatal: cannot describe' message Ping Yin
2008-03-13 17:56 ` [PATCH 2/7] git-submodule: Extract functions module_info and module_url Ping Yin
2008-03-13 17:56 ` [PATCH 3/7] git-submodule: Extract absolute_url & move absolute url logic to module_clone Ping Yin
2008-03-13 17:56 ` [PATCH 4/7] git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config Ping Yin
2008-03-13 17:56 ` [PATCH 5/7] git-submodule: Extract module_add from cmd_add Ping Yin
2008-03-13 17:56 ` [PATCH 6/7] git-submodule: multi-level module definition Ping Yin
2008-03-13 17:56 ` [PATCH 7/7] git-submodule: Don't die when command fails for one submodule Ping Yin
2008-03-14 14:20 ` [PATCH 6/7] git-submodule: multi-level module definition Ping Yin
2008-03-13 18:16 ` [PATCH 0/7] git-submodule enhancements Ping Yin
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=1205431001-18590-1-git-send-email-pkufranky@gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).