Great


> On Aug 20, 2019, at 7:22 PM, Fande Kong <fdkong...@gmail.com> wrote:
> 
> Never mind. I updated everything to point to gitlab. Everything looks fine 
> for me now.
> 
> 
> Fande 
> 
>> On Aug 20, 2019, at 6:05 PM, Smith, Barry F. <bsm...@mcs.anl.gov> wrote:
>> 
>> 
>> Is it so difficult for you to change the link in your test system to 
>> petsc-pre-gitlab?
>> 
>> Barry
>> 
>> 
>>> On Aug 20, 2019, at 4:40 PM, Fande Kong via petsc-dev 
>>> <petsc-...@mcs.anl.gov> wrote:
>>> 
>>> Any way to have the link https://bitbucket.org/petsc/petsc valid (read 
>>> only) for a couple of weeks?  We have some tests that dynamically picks up 
>>> a particular version of PETSc (master, maint, tag).  The link was removed 
>>> now,  and that disabled us to have daily tests. If we could keep this link 
>>> for a couple of weeks, that will give me a grace period to update all the 
>>> impacted tests. 
>>> 
>>> Any particular reason that we have to rename petsc to petsc-pre-gitlab?
>>> 
>>> Thanks,
>>> 
>>> Fande Kong, 
>>> 
>>> On Tue, Aug 20, 2019 at 2:52 AM Lisandro Dalcin via petsc-dev 
>>> <petsc-...@mcs.anl.gov> wrote:
>>> Dear Satish, are you planning to migrate petsc4py?
>>> 
>>> On Mon, 19 Aug 2019 at 23:47, Balay, Satish via petsc-dev 
>>> <petsc-...@mcs.anl.gov> wrote:
>>> A note:
>>> 
>>> The bitbucket repository is saved at 
>>> https://bitbucket.org/petsc/petsc-pre-gitlab 
>>> 
>>> The git part is now read-only. The other parts [issues, PRs, wiki etc] are 
>>> perhaps writable - but we should avoid that.
>>> 
>>> Satish
>>> 
>>>> On Mon, 19 Aug 2019, Smith, Barry F. via petsc-dev wrote:
>>>> 
>>>> 
>>>> 
>>>>  PETSc folks.
>>>> 
>>>>   This announcement is for people who access PETSc from the BitBucket 
>>>> repository or post issues or have other activities with the Bitbucket 
>>>> repository
>>>> 
>>>>  We have changed  the location of the PETSc repository from BitBucket to 
>>>> GitLab. For each copy of the repository you need to do
>>>> 
>>>>  git remote set-url origin 
>>>> g...@gitlab.com<mailto:g...@gitlab.com>:petsc/petsc.git
>>>>  or
>>>>  git remote set-url origin https://gitlab.com/petsc/petsc.git
>>>> 
>>>>  You will likely also want to set up an account on gitlab and remember to 
>>>> set the ssh key information
>>>> 
>>>>  if you previously had write permission to the petsc repository and cannot 
>>>> write to the new repository please email 
>>>> bsm...@mcs.anl.gov<mailto:bsm...@mcs.anl.gov> with your GitLab
>>>>  username and the email used
>>>> 
>>>>   Please do not make pull requests to the Gitlab site yet; we will be 
>>>> manually processing the PR from the BitBucket site over the next couple of
>>>>   days as we implement the testing.
>>>> 
>>>>   Please be patient, this is all new to use and it may take a few days to 
>>>> get out all the glitches.
>>>> 
>>>>   Thanks for your support
>>>> 
>>>>   Barry
>>>> 
>>>>  The reason for switching to GitLab is that it has a better testing system 
>>>> than BitBucket and Gitlab. We hope that will allow us to test and manage
>>>>  pull requests more rapidly, efficiently and accurately, thus allowing us 
>>>> to improve and add to PETSc more quickly.
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Lisandro Dalcin
>>> ============
>>> Research Scientist
>>> Extreme Computing Research Center (ECRC)
>>> King Abdullah University of Science and Technology (KAUST)
>>> http://ecrc.kaust.edu.sa/
>> 

Reply via email to