-| As of git 1.5.3, there is a concept known as [http://en.wikibooks.org/wiki/Git/Submodules_and_Superprojects|super modules]
-|
+| width=45% | As of git 1.5.3, there is a concept known as [http://en.wikibooks.org/wiki/Git/Submodules_and_Superprojects|submodules] The [http://rklophaus.com/articles/20100124-SubmodulesAndSubreposDoneRight.html|subgit] script wrapper is available.
+| width=45% | Mercurial has subrepos that support multiple VCS systems including CVS, subversion, and git. The [http://rklophaus.com/articles/20100124-SubmodulesAndSubreposDoneRight.html|subhg] script wrapper is available.
|-
! Keywords
| "[http://www.gelato.unsw.edu.au/archives/git/0610/28891.html| keyword substitution is just stupid]" - Linus in his trademark @$$hole attitude. Do some scripty stuff is his answer. No SCM support during build/export for tagging files with a release marker. [/nickpalmer] will develop a release script that handles this for us. The reason it might be regarded is stupid is that you can track every tag and branch to a SHA id, providing precise knowledge of the state of the code for a release (assuming one might use a tag for a release). Consider how jquery uses tags on github to denote release versions.
@@ -31,6 +31,10 @@
| #Migrate each module separately, and [http://stackoverflow.com/questions/12843/how-to-combine-two-projects-in-mercurial|then combine]
|-
+!CIA/IRC notifications
+|There are three scrips - ciabot.pl which is old, ciabot.sh which is configuration free, and ciabot.py which is fast. For the central repo, the following like should be added to foo.git/hooks/update (one line is broken here simply for formatting of his comparison table):{code source=bash}/home/git/ciabot.py ${refname} \