Changes between Version 2 and Version 3 of GitSubmoduleProblem


Ignore:
Timestamp:
Sep 9, 2013 8:05:51 AM (23 months ago)
Author:
hvr
Comment:

more notes about git submodules

Legend:

Unmodified
Added
Removed
Modified
  • GitSubmoduleProblem

    v2 v3  
    88 - based on the current access patterns, a few repositories are modified often (specifically,  ghc.git and testsuite.git are often updated in a inter-dependent way); most repositories aren't updated for several weeks; therefore some of the issues outlined with the usability of submodules might have less weight here.
    99
    10  - Simple migration plan:
    11     - Fold testsuite.git into ghc.git, as they are strongly inter-dependent. nofib.git and base.git are two other candidates for being folded into ghc.git.
    12     - All other add-on repositories should be converted into Git submodules.
     10=== Simple migration plan ===
     11
     12The plan:
     13
     14 - Fold testsuite.git into ghc.git, as they are strongly inter-dependent. nofib.git and base.git are two other candidates for being folded into ghc.git.
     15 - All other add-on repositories should be converted into Git submodules.
     16
     17The consequences:
     18
     19 - `ghc.git`'s commit id by itself effectively provides a sufficient source-tree fingerprint; therefore, this renders the `fingerprint.py` superfluous
     20
     21 - `git bisect` works (almost) out of the box now
     22
     23 - buildbots don't need to fetch all repos *every time* to check for new commits; it's enough to check `ghc.git`, and only if a new commit in `ghc.git` exists, run `git submodule update`
     24