[vtk-developers] Keeping in fork in sync

[Bill Lorensen]

I'm not sure what happened when I did the initial setup.

To fix it, I removed the upstream and origin from my config file and
reran the setup script. I am OK now. Here is the result:
master)] git remote -v
gerrit lorensen at review.source.kitware.com:VTK (fetch)
gerrit lorensen at review.source.kitware.com:VTK (push)
gitlab https://gitlab.kitware.com/lorensen/vtk.git (fetch)
gitlab git at gitlab.kitware.com:lorensen/vtk.git (push)
origin https://gitlab.kitware.com/vtk/vtk.git (push)
origin https://gitlab.kitware.com/vtk/vtk.git (fetch)
stage git://vtk.org/stage/VTK.git (fetch)
stage git at vtk.org:stage/VTK.git


On Thu, Mar 19, 2015 at 5:47 AM, Brad King <brad.king at kitware.com> wrote:
> On 03/18/2015 10:33 PM, David Gobbi wrote:
>> So the issue is that your "origin" is set to your fork, rather
>> than to the main repository.   Unless origin is the main repo,
>> the recipes we're posing will not work.
>
> Running the Utilities/SetupForDevelopment.sh script as was described
> in the initial transition instructions should have prompted you to
> change origin to the main repo on gitlab.kitware.com, not your fork.
>
> Some documentation in the wild (for Github IIRC) suggests cloning
> from your fork and adding the upstream repository as a remote
> called "upstream".  Our documented workflow does *not* do this.
> We prefer to keep "origin" meaning the same thing for everyone.
>
> -Brad
>



-- 
Unpaid intern in BillsBasement at noware dot com