Changes between Version 3 and Version 4 of GitSubmoduleProblem


Ignore:
Timestamp:
Jun 21, 2014 12:26:48 PM (5 years ago)
Author:
thomie
Comment:

Delete, and link to GitRepoReorganization

Legend:

Unmodified
Added
Removed
Modified
  • GitSubmoduleProblem

    v3 v4  
    1 Lorem ipsum...
    2 
    3 
    4 == some misc. notes about submodules ==
    5 
    6 See also some older notes: DarcsConversion#Theperspectiveonsubmodules
    7 
    8  - 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.
    9 
    10 === Simple migration plan ===
    11 
    12 The 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 
    17 The 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 
     1This page is obsolete; please update links to point to GitRepoReorganization.