From: Gelonida N <gelonida@gmail.com>
To: git@vger.kernel.org
Subject: git diff --numstat <branch> always shows dirty submodules
Date: Sat, 12 Nov 2011 14:29:36 +0100 [thread overview]
Message-ID: <j9lsc1$4uf$1@dough.gmane.org> (raw)
Hi,
I recently started using submodules and they behave mostly as I like to.
Normally I use diff --numstat <branch>
to check quickly whether I am aligned with another branch or not.
The (for me) annoying feature of submodules is, that they are always
reported to be different due to files, which are not under git.
I type git diff --numstat master
I get
1 1 mysubmodule
Now I check the differences with git diff master mysubmodule
diff --git a/mysubmodule b/mysubmodule
index 1382b73..f4f1f1d 160000
--- a/mysubmodule
+++ b/mysubmodule
@@ -1 +1 @@
-Subproject commit xxxxxxxxx
+Subproject commit xxxxxxxxx-dirty
So the only difference (which I wasn't interested in) is, that the
submodule is dirty.
Is there any quick way flag / helper script / . . .
to show differences between two branches without raising the fact, that
submodules are dirty?
>From a user perspective I don't see why this is reported.
I am not being warned about dirty files in the top level repository
next reply other threads:[~2011-11-12 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 13:29 Gelonida N [this message]
2011-11-12 20:02 ` git diff --numstat <branch> always shows dirty submodules Jens Lehmann
2011-11-13 0:45 ` Gelonida N
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='j9lsc1$4uf$1@dough.gmane.org' \
--to=gelonida@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).