OK. So are you saying that you can't reliably change to a different branch in an existing tree, but rather must freshly clone from the source each time you want to check out a different branch? That seems a bit extreme. I thought switching branches is precisely what git is good at. Still I'll blow away my tree and try what you say. Simon | -----Original Message----- | From: Herbert Valerio Riedel [mailto:hvriedel@gmail.com] | Sent: 24 April 2014 11:30 | To: Simon Peyton Jones | Cc: Austin Seipp | Subject: Re: Cloning ghc-7.8 | | On 2014-04-24 at 12:14:16 +0200, Simon Peyton Jones wrote: | > I tried the sequence below and got this: | | maybe try this sequence that was suggested by Austin on #ghc a couple | of | days ago: | | <thoughtpolice> (sync-all has a little difficulty with the submodules | here, and you'll end up needing to always clean anyway due to interface | changes, etc) | <thoughtpolice> 'git clone -b ghc-7.8 git://git.haskell.org && cd ghc | && ./sync-all get -b ghc-7.8' should do it |
On 2014-04-24 at 12:38:40 +0200, Simon Peyton Jones wrote:
OK. So are you saying that you can't reliably change to a different branch in an existing tree, but rather must freshly clone from the source each time you want to check out a different branch?
That seems a bit extreme. I thought switching branches is precisely what git is good at.
In all fairness, you made it sound (e.g. Subject-line) as if you wanted to know how to *clone* a GHC 7.8 branch rather than switching to the ghc-7.8 branch... :-) That said, however: Yes, switching between the 'ghc-7.8' branch and 'master' is currently problematic, because 'ghc-7.8' has a different mix of submodules and loose subrepos than 'master', and the issue being that Git isn't aware of that, so Git gets confused here and there, as it doesn't have all information it needs. This will get better however, once everything is put under Git's control. Then switching between 'ghc-7.10' and GHC HEAD should work much smoother than now between 'ghc-7.8' and GHC HEAD Hope this makes some sense...
On Thu, Apr 24, 2014 at 12:38 PM, Simon Peyton Jones
That seems a bit extreme. I thought switching branches is precisely what git is good at.
It was made not so great in the past (i.e. 7.8) by us having the homegrown sync-all pull system instead of submodules.
participants (3)
-
Herbert Valerio Riedel -
Johan Tibell -
Simon Peyton Jones