#1918: Branch changes in the thornlist are ignored when updating ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: GetComponents | Version: development version Keywords: | ---------------------------+------------------------------------------------ When updating an existing GetComponents checkout, if the branch has changed in the thornlist, the old branch is checked out, so the result of running GetComponents --update is to ignore the new branch in the thornlist.
#1918: Branch changes in the thornlist are ignored when updating ----------------------------+----------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: confirmed Priority: major | Milestone: Component: GetComponents | Version: development version Resolution: | Keywords: ----------------------------+----------------------------------------------- Changes (by knarf):
* status: new => confirmed
Comment:
The code seems to specifically implement that behavior: - It updates all branches that were specified to the 'update' command, plus 'master' (last). The branches that are specified are all branches specified for REPO_BRANCH, delimited by comma. - It then switches back to the branch that the repository was at before the update.
In this sense, it does an 'update', not a 'switch to another branch'. Now the question is what we want GetComponents to do when given the command to 'update'.
trac@lists.einsteintoolkit.org
-
Einstein Toolkit