Hi folks. I've seen some people abandon a change on master, and then reupload the same change to develop. This will work, but it's unnecessary and will disconnect the change's history. To migrate the change from one branch to the other, you can use the "Move change" option in the gerrit UI which is near "REBASE", "ABANDON", and "EDIT", but slightly hidden in the menu behind the three vertical dots.
That will move you change to a new branch (enter "develop" where indicated), and that should then show up over on the left in the panel of properties of the review under "Repo Branch" which will, unsurprisingly, show the repo name and the branch for this change. Then if you want to upload a new version, you can use "git branch --set-upstream-to origin/develop" on your local branch. This tells git that the branch with your change branches off of develop now, and not master. Since develop is a superset of master, that should be pretty straightforward for git to do and shouldn't really change anything structurally with your branch. Then you can "git rebase" just to move your change up to the current end of develop. If you then "git push origin HEAD:refs/for/develop", that should update your existing review in place without creating a new review and disconnecting the review history. Gabe _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
