ParaView/Git/Maintain: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
| Line 27: | Line 27: | ||
:<code>$ ./Utilities/SetupForDevelopment.sh</code> | :<code>$ ./Utilities/SetupForDevelopment.sh</code> | ||
|} | |} | ||
==Gatekeeper Review Script== | |||
<code lang="python"> | |||
</code> | |||
==Miscellaneous Commands== | ==Miscellaneous Commands== | ||
Revision as of 17:53, 28 September 2012
This page documents how to maintain ParaView branches through Git.
See our table of contents for more information.
Merging next topics into master
Before you begin, perform initial setup:
|
1. | |
|
2. | |
|
|
|
3. | |
|
Gatekeeper Review Script
Miscellaneous Commands
- Show branches merged in next or master on stage
$ git fetch stage -p$ git branch -r --merged stage/next | grep stage$ git branch -r --merged stage/master | grep stage
- Find the SHA1 for the VTK submodule that a branch is referring to.
$ git ls-tree <branchname> VTK | awk '{print $3}'
