[Paraview-developers] New git repo: reporting changed repo after only pull

[Moreland, Kenneth]

Yes.  That seems to fix the problem.  However, is there a way to get ctest to run that after pulling?  Otherwise we'll still get a bunch of errors in the dashboard.

-Ken


On 4/19/10 5:09 PM, "Dave Partyka" <dave.partyka at kitware.com> wrote:

does 'git submodule update' help?

On Mon, Apr 19, 2010 at 7:02 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
I noticed something odd when converting to the new git repositories today.  After only cloning the repository, setting up the modules, and then pulling (using the --rebase flag as described on the Wiki), status reports that I have made a change in my repository even though I have not.  Here is a terminal capture of a newly cloned ParaView repository (after modules and hooks are set up).

kmorel2 0> git status                                /Users/kmorel/src/ParaView
# On branch master
nothing to commit (working directory clean)
kmorel2 1> git pull --rebase                         /Users/kmorel/src/ParaView
remote: Counting objects: 44, done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 26 (delta 20), reused 0 (delta 0)
Unpacking objects: 100% (26/26), done.