“git pull” and “git submodule update” seem to have worked for 5.3.0-RC2.
________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel <ben.boec...@kitware.com> Reply-To: "ben.boec...@kitware.com" <ben.boec...@kitware.com> Date: Wednesday, February 22, 2017 at 9:04 AM To: Rick Angelini <richard.c.angelini....@mail.mil> Cc: Cory Quammen <cory.quam...@kitware.com>, ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Wed, Feb 22, 2017 at 13:10:04 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cory - so I did a “git pull” and “git submodule update” in my existing > paraview-superbuild repository directory and that 5.3.0-RC1 information > was not in the versions.cmake file. I did a clean “git clone” and I > then received the correct files. I’m not a git expert - so I’m not > sure why I had to do a clean “git clone”. I thought I “git pull” should > have done a proper update. I must be missing something with my > repository update commands ….. What is the output of the following commands: - git config branch.master.remote - git remote show $output_from_previous_command - git remote show origin --Ben
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
