Changes between Version 3 and Version 4 of faq/gitification
- Timestamp:
- May 25, 2012, 6:25:46 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
faq/gitification
v3 v4 6 6 7 7 Since a Drupal website is not a monolithic bloc and nearly each module is maintained by different developers we needed to find a way to update the core and each module separately from one another. The traditional way git offers for this is a concept called [http://git-scm.com/book/en/Git-Tools-Submodules git-submodule]. It complicated, unintuitive and detested by many for good reasons. But as git follows the [http://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it TMTOWTDI] paradigm we could avoid using git-submodule and settled for [https://github.com/apenwarr/git-subtree git-subtree] instead which has recently been [https://github.com/apenwarr/git-subtree/commit/8cd698957f57f62ec3d313403bebced2fdf751e5 merged] into git core. Besides the possibility to update the core and each module separately and replaying our patches to the updated version automatically, we want the linksunten code to be one git repository which simply "works" after cloning it. After our move to git we will use the [http://drupal.org/project/features features] module to version control as much of our configuration data as possible. 8 9 == Drupal core == 10 11 We create a new directory, initialise git, add pressflow as a new remote and fetch it: 12 {{{ 13 mkdir liu_d6 14 cd liu_d6 15 git init 16 git remote add pressflow-6.x git://github.com/pressflow/6.git master 17 git fetch pressflow-6.x 18 }}}