Last modified: 2013-03-27 17:32:17 UTC
I didn't realize Gerrit would mistake my 'debian' branch for a topic and merge it onto master. The guidelines for using git to manage packages stipulate that there should be a correlation between the commit history and the package changes, so fixing this by creating a new change would not be ideal. I poked ^demon and paravoid on IRC about this a few weeks ago and we agreed deletion / recreation would be best, but it was not yet possible because the migration to Gerrit 2.5 was just starting.
Given our gerrit's version number, I guess, we're currently on Schema#76. For this schema, deleting projects is not yet possible. It will be possible once https://gerrit-review.googlesource.com/#/c/43143/ has been merged upstream, and after we deployed a new "delete-project" plugin to our gerrit instance.
Also, that's git-review that assumes local branch -> topic for merging to defaultbranch...so it's not really gerrit's fault :\
(In reply to comment #2) > Also, that's git-review that assumes local branch -> topic for merging to > defaultbranch...so it's not really gerrit's fault :\ Chad, understood. It's not a question of assigning fault (it is my entirely my own), but of helping me to undo it, if possible. Is Christian right that this not currently doable?
I'm trying to make sure we know which tool caused the problem :) This is almost doable. The required changes have almost gone into the upstream plugin, at which point I'll deploy it.
We deleted this, right?
Yup. Otto recreated it properly in Ia7a875f4e. Thanks.
