<div class="gmail_quote">On Sat, Aug 21, 2010 at 10:47 PM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Sat, Aug 21, 2010 at 4:14 PM, pat marion <span dir="ltr"><<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Did you try git submodule update? (Might need 'git submodule init' first)<br><br>Pat<br><br></blockquote><div>
<br></div></div><div>Thanks Pat, 'git submodule update' did the trick. I added a section to the wiki page:</div><div><br></div><a href="http://www.paraview.org/Wiki/ParaView/Git#Typical_Users_Workflow" target="_blank">http://www.paraview.org/Wiki/ParaView/Git#Typical_Users_Workflow</a></div>
<div class="gmail_quote"><br></div><div class="gmail_quote">While it is nice to have all of the details, I think this should help people who just want to stay current with ParaView but don't care about learning git (and have no intention of editing/contributing code). Let me know if it seems reasonable (and correct!).</div>
</blockquote><div><br></div><div>There was a lot more than was needed, so I updated it. Basically, the initial clone creates the ParaView directory, initializes and then updates the submodule. So only one command is required for initial checkout. To update, you must first pull, and then update the submodules (the pull is what may push the submodule forward).</div>
<div><br></div><div>I hope that makes things clearer. I agree that we need to provide very brief, minimal instructions for people that just want to get up and running as quickly as possible.</div><div><br></div><div>Thanks,</div>
<div><br></div><div>Marcus</div><div>--</div>Marcus D. Hanwell, Ph.D.<br>R&D Engineer, Kitware Inc.<br>(518) 881-4937 </div>