Submodule update#792
Conversation
|
Job VTB Documentation, step Sync Docs on a54d38a wanted to post the following: View the site here This comment will be updated on new commits. |
|
looks like we have diffs in VTR from BISON, probably due to change in blas? |
|
What is the status of this PR? I want a submodule update as well. Or should I do a separate PR? |
|
Do a separate PR, updating only the modules you need |
|
@YaqiWang I've been on travel this week with other meetings. I'll be available to return to this later this afternoon. I'll handle any conflicts with any other PR you use to update specific submodules. |
Refs #0
7bd29e1 to
a54d38a
Compare
|
Might be a good idea to wait for this a bit. I was intending to update moose and griffin, but I do not feel quite comfortable of updating moose without updating other applications. If we have any hard stoppers in here, I will proceed my own update. |
It's common some of the other applications will have a different moose in their submodule than the moose submodule that is in VTB. Feel free to push your changes with the updates. This had just sat for a week or so I was bringing it up to date with the latest master/main branches. I can handle any conflicts/remove the submodule update of the individual apps if you want to move forward with yours separately. |
@gambka I'm in the process of updating SAM in #791, but that will be to |
This PR was generated by running the following command from the repository root:
python submodule_updater.py ../
Updates application submodules:
Updating submodules