Elia Pinto's patch starts from a reproduction. A user clones an empty bare repository, commits, and runs git status. It reports that the branch is based on 'origin/master' but the upstream is gone, and suggests "git branch --unset-upstream". Pinto argues the upstream was never there, since the remote is empty and origin/master has not been created. The advice is also wrong for the user, because "git push" would create origin/master and make the message disappear.
The wording came from f2e087395b (branch: report invalid tracking branch as gone, 2013-08-26), which assumed a configured upstream that cannot be resolved had been deleted. The patch rewords the message to say the upstream does not exist.
Junio C Hamano said he agrees with the diagnosis and called "does not exist" clever because it covers both cases. He suggested a short form such as "missing" could be reused elsewhere, for instance inside [] in place of [gone]. He also asked whether the "git push" suggestion is emitted unconditionally and whether an immediate push always creates the upstream, or whether the code must check first.
Harald Nordgren noted that Pinto had already posted the same patch earlier, and the thread has since had a repost.