Closed mdpiper closed 9 years ago
@mperignon & @Elchin: What do you think of this?
My goal is to create a branch for each WMT project by deleting (!) all components not used in the project. This is wrong, in that if I modify any component in a branch, I can't pull it back into the master. However, as @mcflugen pointed out, we can develop on master, and rebase a project branch as needed. So master -> branch is OK, but branch -> master is very bad.
@mdpiper, I think I understand what you are describing. Would selective merging get around the problem of merging individual changes in branches to master? I haven't tried this but it sounds like it might work: https://gist.github.com/katylava/564416
@mperignon Yeah, this looks like what would be needed for merging branch -> master. Thanks for finding this info.
This branch is a subset of the CSDMS component library containing only the components related to the "hydrology" project -- currently, the TopoFlow components.
When setting up the component metadata for this project on the WMT database server, clone this branch, not the master branch. E.g., on _river_: