On 19 June 2011 09:40, Ian Lynagh <[email protected]> wrote: > On Sat, Jun 18, 2011 at 08:24:26PM -0700, David Terei wrote: >> Yeah sorry. There is a Cabal patch that hasn't seem to come through to >> the GHC Cabal lag repo yet. I tried to force a manual update of the >> Cabal lag repo but no luck. My understanding is that the lag repo is >> meant to be sync'd once a day but this doesn't seem to be happening. >> So either something is broken with the Cabal lag or my understanding >> of the situation is wrong. > > For future reference, you always need to manually push to the GHC repos > (after validating). It's just that you need to push to the upstream > repos, and the mirrors need to update, first.
Sorry I'm not sure I understand this. My best interpretation is this: 1) I develop a new Cabal feature that GHC will use. 2) I push the patch for it to upstream (which is a darcs repo). 3) There is an automatically sync'd git mirror of the upstream darcs repo. Lets call it G. I thought G corresponded to the git repo that is used in a GHC dev tree, usually located at http://darcs.haskell.org/packages/Cabal.git. You seem to be saying this isn't the case, G is somewhere else. 4) The Cabal git repo in the GHC dev tree (the one at http://darcs.haskell.org/package/Cabal.git, lets call in G2) is not auto sync'd. Instead after doing step 2 and waiting for step 3 to happen, I must manually push from G to G2. Is this correct or crazy talk? If correct, where is repo G located? Cheers, David _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
