From: "Yin Ping" <pkufranky@gmail.com>
To: git@vger.kernel.org
Subject: Issues for git-submodule
Date: Sat, 20 Oct 2007 15:31:00 +0800 [thread overview]
Message-ID: <46dff0320710200031x2a58706cl7d3df11cad12d4d2@mail.gmail.com> (raw)
In-Reply-To: <46dff0320710200027o5fe434b4i9bd4f3ffc17f03f6@mail.gmail.com>
1. gti-submodule status
As the manual says, '+' is shown if the currently checked out
submodule commit does not match the SHA-1 found in the index of the
containing repository.
However, not matching has two cases: one is a new commit in the
submodule, the other is update of index of the submodule after a
command such as "git-pull".
So which is the case when a '+' is seen? Should i run 'git-commit'
or 'git-submodule update'? As a suggestion, I think git should tell
the user which commit is newer (the one in supermodule index or the
HEAD of the submodule) and even give the log entry between the two
commits.
2. As I first saw 'git-submodule status submoduepath', I thought it
should do the following thing
cd submoduepath && git-status && cd -
This is actually what i need, espacially when i have a lot of
submodules and has made changes in some modules. How do i know which
modules have been changed and how they have been changed?
So, In some degree, I even think current 'git-submodule status'
should be replaced by git-status and the right thing 'git-submodule
status' should do is to show the status of submodule itself as i just
said above.
--
franky
parent reply other threads:[~2007-10-20 7:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <46dff0320710200027o5fe434b4i9bd4f3ffc17f03f6@mail.gmail.com>]
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=46dff0320710200031x2a58706cl7d3df11cad12d4d2@mail.gmail.com \
--to=pkufranky@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 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).