[Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

“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.boeckel at kitware.com>
Reply-To: "ben.boeckel at kitware.com" <ben.boeckel at kitware.com>
Date: Wednesday, February 22, 2017 at 9:04 AM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: Cory Quammen <cory.quammen at kitware.com>, ParaView
<paraview at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170223/24a50247/attachment.bin>