Comment 1 for bug 1064939

This is going to become more common now that 1.21 doesn't set a topic if the local branch name is the same as the remote branch (for example a developer working on master instead of in a topic branch). When you download a topic-less change with git review -d it will set the local topic branch name such that it ends with the change number. Any subsequent patchset or changes appended within that topic branch will get checked in with that change number as the new topic.

For me, this side effect of 2e27fad is unexpected, but I'm not convinced the behavior is necessarily disruptive (though I agree it has the potential to be somewhat misleading). I'm also not sure what a good fix would be for this--suggestions welcome.