From: "Ping Yin" <pkufranky@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, "Ping Yin" <pkufranky@gmail.com>
Subject: Re: [PATCH v2 1/3] git-submodule summary: --for-status option
Date: Thu, 10 Apr 2008 23:57:36 +0800 [thread overview]
Message-ID: <46dff0320804100857y2037263fodb7795e0ff33cd0c@mail.gmail.com> (raw)
In-Reply-To: <1207842625-9210-3-git-send-email-pkufranky@gmail.com>
On Thu, Apr 10, 2008 at 11:50 PM, Ping Yin <pkufranky@gmail.com> wrote:
>
> The --for-status option is mainly used by builtin-status/commit.
> It adds 'Modified submodules:' line at top and '# ' prefix to all
> following lines.
>
Sorry for the repeated mail. I don't know how it happened. Maybe
send-email bug or my misoperation.
So just Ignore the second one.
--
Ping Yin
next prev parent reply other threads:[~2008-04-10 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 15:50 [PATCH/RFC] submodule: fallback to .gitmodules and multiple level module definition Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 1/7] git-submodule: Extract functions module_info and module_url Ping Yin
2008-04-10 15:50 ` [PATCH v2 1/3] git-submodule summary: --for-status option Ping Yin
2008-04-10 15:50 ` [PATCH v2 2/3] builtin-status: submodule summary support Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 2/7] git-submodule: Extract absolute_url & move absolute url logic to module_clone Ping Yin
2008-04-10 15:50 ` [PATCH v2 3/3] buitin-status: Add tests for submodule summary Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 3/7] git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 4/7] git-submodule: Extract module_add from cmd_add Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 5/7] git-submodule: multi-level module definition Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 6/7] git-submodule: Don't die when command fails for one submodule Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 7/7] git-submodule: "update --force" to enforce cloning non-submodule Ping Yin
2008-04-11 23:24 ` [PATCH/RFC 3/7] git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config Junio C Hamano
2008-04-11 23:24 ` Junio C Hamano
2008-04-12 4:26 ` Ping Yin
2008-04-11 21:56 ` [PATCH/RFC 2/7] git-submodule: Extract absolute_url & move absolute url logic to module_clone Junio C Hamano
2008-04-12 2:56 ` Ping Yin
2008-04-10 15:57 ` Ping Yin [this message]
2008-04-11 22:30 ` [PATCH/RFC 1/7] git-submodule: Extract functions module_info and module_url Junio C Hamano
2008-04-12 3:05 ` Ping Yin
2008-04-12 4:50 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 15:35 [PATCH v2] builtin-status: submodule summary support Ping Yin
2008-04-10 15:35 ` [PATCH v2 1/3] git-submodule summary: --for-status option 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46dff0320804100857y2037263fodb7795e0ff33cd0c@mail.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.
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).