How curious! Some clarification would definitely be appreciated. _ara

On 20 Dec 2018, at 17:40, Gabor Greif wrote:

(To: Ben added directly)

Yes, https://gitlab.haskell.org/ghc/ghc still seems to mirror https://:*****@git.haskell.org/ghc, so the cutover is not complete yet.

OTOH, the Gitlab instance allowed me to merge a request (which did not work yesterday), so /something/ has changed. The interesting consequence is now that https://gitlab.haskell.org/ghc/ghc fails to sync with its master.

Another thing missing is to redirect the github mirror (https://github.com/ghc/ghc), too.

Cheers,

Gabor

...

On 12/20/18, Ara Adkins wrote: Hey All,

Sorry for my confusion, but I'm a bit unclear as to when we're meant to start working against the GHC repo on the gitlab.haskell.org instance. I had in mind that the cutover was intended to be the 18th, but going on there it still appears as if it's mirrored from git.haskell.org. Can somebody clarify this for me?

Best, _ara

Perfect. Thanks for the clarification Ben! _ara

On 21 Dec 2018, at 16:55, Ben Gamari wrote:

Ara Adkins writes:

...

Hey All,

Sorry for my confusion, but I'm a bit unclear as to when we're meant to start working against the GHC repo on the gitlab.haskell.org instance. I had in mind that the cutover was intended to be the 18th, but going on there it still appears as if it's mirrored from git.haskell.org. Can somebody clarify this for me?

Sorry for the confusion. I have been reluctant to formally announce the cut-over until CI is green but this has taken a fair bit longer than anticipated due to the long CI cycle time. Nevertheless people have started submitting MRs against the GitLab instance and you are more than welcome to do so.

As far as the official upstream repository, indeed gitlab.haskell.org/ghc/ghc is still mirroring git.haskell.org/ghc. This will change when I formally announce the switchover.

Cheers,

- Ben