! Feature !! Git !! Mercurial
|
|-
|
! Ad-hoc Builds
|
-| 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.
|
-| 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.
|
+| 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.
|