That doesn't show the changes though.

What i'd expect to happen is that when you update the link to a subproject, it would show the diff between the 2 revisions. 

For instance, if you run git diff mantis-1.2.7...mantis-1.2.8 I should get a diff of ALL changes between the two releases regardless of where the change has happened.


On Mon, Mar 3, 2014 at 7:47 PM, Damien Regad <> wrote:
On 03.03.2014 18:37, Paul Richards wrote:
>     b) Go back to having everything in a single repository so it's easy
>     to diff changes between two git revisions - and not having to work
>     out seperately if a submodule might have changed

I think you're still missing the point that changes that happen in the
submodules, should be tracked *in the relevant repository* and not in

You can still easily find out that a submodule has changed, e.g.

$ git diff master~10 -- library/
diff --git a/library/adodb b/library/adodb
index 1208307..c1abd33 160000
--- a/library/adodb
+++ b/library/adodb
@@ -1 +1 @@
-Subproject commit 1208307846b90c9d5594f3163451c5039c45bbef
+Subproject commit c1abd33cf8f4c67a98f559a0028f39d8194b21f0

This email is free from viruses and malware because avast! Antivirus protection is active.

Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
mantisbt-dev mailing list