Repository Reorganization Question

[Simon Peyton-Jones]

What (if anything) do we need to do when updating existing local repos.  Will everything be ok if I just do 
   sync-all pull

Simon

| -----Original Message-----
| From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of
| Herbert Valerio Riedel
| Sent: 05 December 2013 11:15
| To: ghc-devs at haskell.org
| Subject: Re: Repository Reorganization Question
| 
| On 2013-12-05 at 11:17:01 +0100, Herbert Valerio Riedel wrote:
| 
| [...]
| 
| > Fyi, I've drafted how the change would look like in the new ghc.git
| > branch 'wip/T8545' so we can test/evaluate the effects/fallout before
| > peforming this operation on 'master'.
| >
| > So running
| >
| >  git clone -b wip/T8545 git://git.haskell.org/ghc.git
| >  cd ghc/
| >  ./sync-all get
| >
| > should result in a new checkout including the folded-in testsuite/
| > folder.
| 
| PS: I didn't merge in testsuite's Git history as that would bloat
|     ghc.git quite a bit; however, 'git blame' functionality can be
|     recovered in a local checkout by using something like Git's
| grafting
|     feature:
| 
|     # make available old testsuite Git objects in local ghc.git
|     git remote add -f old-testsuite git://git.haskell.org/testsuite.git
| 
|     # add 2nd parent commit to e45b9f57a90 pointing to testsuite.git
|     echo e45b9f57a9044e8a20e3cc13bcff86b12b3da405 \
|          1860dae3a7e377f085f3a4134f532a7f577fccbe \
|          3e66489ebcef0f4cd86968c6781a1d4ad1981f94 > .git/info/grafts
| 
|     This way when peforming 'git blame' on files in the the testsuite/
|     folder results in sensible information dating back before the
|     history-cut-off point.
| 
| _______________________________________________
| ghc-devs mailing list
| ghc-devs at haskell.org
| http://www.haskell.org/mailman/listinfo/ghc-devs