Simon Marlow writes:
> Congrats Ben and co! This is a huge step forwards.
>
Thanks!
> submodules are still pulling from git.haskell.org, is there an easy way to
> fix that?
Indeed, Omer's advice is spot on.
Cheers,
- Ben
signature.asc
Description: PGP signature
> submodules are still pulling from git.haskell.org, is there an easy way to
> fix that?
`git submodule sync` should fix that.
Ömer
Simon Marlow , 7 Oca 2019 Pzt, 11:42 tarihinde şunu yazdı:
>
> Congrats Ben and co! This is a huge step forwards.
>
> On Thu, 27 Dec 2018 at 06:27, Ben Gamari wro
Congrats Ben and co! This is a huge step forwards.
On Thu, 27 Dec 2018 at 06:27, Ben Gamari wrote:
>
> git remote set-url origin https://gitlab.haskell.org/ghc/ghc.git
> git remote set-url --push origin g...@gitlab.haskell.org:ghc/ghc
>
> This is all that should be necessary; a quick `gi
Am Dienstag, den 01.01.2019, 15:04 -0500 schrieb Ben Gamari:
> Wolfgang Jeltsch writes:
> > What if I create a GitHub-linked GitLab account before the
> > migration? Will this account be used for my Trac stuff in case my
> > GitHub(!) e-mail address is the same as my Trac e-mail address?
>
> I'
Wolfgang Jeltsch writes:
> Am Dienstag, den 01.01.2019, 06:32 -0500 schrieb Ben Gamari:
>>
>> When the Trac migration is carried out new GitLab accounts will be
>> created for Trac users who have not yet created an account. You will
>> be able to request a password reset to gain access to this a
Am Dienstag, den 01.01.2019, 06:32 -0500 schrieb Ben Gamari:
> On December 31, 2018 6:27:33 PM EST, Wolfgang Jeltsch:
> >
> > Am Donnerstag, den 27.12.2018, 01:27 -0500 schrieb Ben Gamari:
> > >
> > > In the meantime, users of Trac should check and possibly update
> > > the email address associat
On December 31, 2018 6:27:33 PM EST, Wolfgang Jeltsch
wrote:
>Am Donnerstag, den 27.12.2018, 01:27 -0500 schrieb Ben Gamari:
>> In the meantime, users of Trac should check and possibly update the
>> email address associated with their account [1]. This address will
>be
>> used to correlate Trac
Am Donnerstag, den 27.12.2018, 01:27 -0500 schrieb Ben Gamari:
> In the meantime, users of Trac should check and possibly update the
> email address associated with their account [1]. This address will be
> used to correlate Trac users with their GitLab equivalents so the
> correctness of this add
Ben Gamari writes:
> Matthew Pickering writes:
>
>> Does this mean that the commit message doesn't come from the MR description?
>>
> Correct. Like GitHub, the commit messages that make it into the version
> control history are precisely the commit messages of the commits in your
> branch.
>
I
Matthew Pickering writes:
> Does this mean that the commit message doesn't come from the MR description?
>
Correct. Like GitHub, the commit messages that make it into the version
control history are precisely the commit messages of the commits in your
branch.
> If I want to edit the commit mess
Thanks ben! Great to know.
CC the list in case anyone else was interested.
_ara
> On 27 Dec 2018, at 15:06, Ben Gamari wrote:
>
> Ara Adkins writes:
>
>> Along the lines of things needing to be adapted, are we moving the
>> ghc-commits mailing list over to GL?
>>
> Yes, although I haven't
Does this mean that the commit message doesn't come from the MR description?
If I want to edit the commit message for a description I need to
1. squash the changes locally
2. force push the branch
3. Wait for CI to finish building (even though I just changed the
commit message).
Matt
On Thu, De
Matthew Pickering writes:
>> To ensure that GHC's git history remains linear ghc/ghc will use GitLab's
>> "fast-forward without a merge commit" merge strategy.
>
> Are merge requests squashed before they are merged?
>
> It seems that the answer by default is no..
> https://gitlab.com/gitlab-org/g
Along the lines of things needing to be adapted, are we moving the ghc-commits
mailing list over to GL?
_ara
> On 27 Dec 2018, at 14:05, Gabor Greif wrote:
>
> Great work, Ben!
>
> Thanks for all the hard work setting up this CI. My hopes are high
> that our contributions' quality and ease w
Great work, Ben!
Thanks for all the hard work setting up this CI. My hopes are high
that our contributions' quality and ease will go up.
There seem to be a few loose ends that need to be wrapped up, like
redirect the mirroring of https://github.com/ghc/ghc/ towards GitLab
and possibly switch on m
Congrats to Ben and everybody involved! This has been a long time coming and
I’m super excited to see what it means for GHC in the future!
_ara
On 27 Dec 2018, at 11:56, Matthew Pickering wrote:
>> To ensure that GHC's git history remains linear ghc/ghc will use GitLab's
>> "fast-forward with
> To ensure that GHC's git history remains linear ghc/ghc will use GitLab's
> "fast-forward without a merge commit" merge strategy.
Are merge requests squashed before they are merged?
It seems that the answer by default is no..
https://gitlab.com/gitlab-org/gitlab-ce/issues/27956
and the reason
I have a patch on phabricator which has finished review and is ready to merge.
https://phabricator.haskell.org/D5458
Should I put it on Gitlab as now all patches should pass CI before being merged?
Matt
On Thu, Dec 27, 2018 at 6:28 AM Ben Gamari wrote:
>
> TL;DR. https://gitlab.haskell.org/ghc
Congratulations, and well done. Changing basic infrastructure is a huge
and thankless job.
Alan
On Thu, 27 Dec 2018 at 08:27, Ben Gamari wrote:
> TL;DR. https://gitlab.haskell.org/ghc/ghc.git is now the official
>upstream GHC repository. Various introductory notes are
>discuss
TL;DR. https://gitlab.haskell.org/ghc/ghc.git is now the official
upstream GHC repository. Various introductory notes are
discussed. Let me know if you have any trouble.
Also, please do verify the correctness of the email address
associated with your Trac account in the
20 matches
Mail list logo
