The patch addresses a case where a user clones an empty repository, commits, and runs git status. The output says the upstream is gone and suggests git branch --unset-upstream. Elia Pinto argues that the upstream was never there, since origin/master has not yet been created, and that the advice is wrong: a git push creates origin/master and the message disappears. The wording dates from f2e087395b, which assumed a configured upstream that cannot be resolved was deleted.
Elia Pinto pinged for review of v2, noting that it is queued in 'seen' as ep/status-missing-upstream, is listed as 'Needs review' in What's cooking, and still merges cleanly with master and seen. She says v2 addresses Junio Hamano's v1 comments, and that the shorter wording 'missing' that he suggested for '[gone]' will arrive as a separate patch.
Harald Nordgren replied that v2 looks good to him. Junio Hamano responded that this and a similar one-line note on the RFC are encouraging, but do not help assess the patch because onlookers cannot tell how deeply the reviewer read the code. He said positive review is harder than pointing out problems but that the project should aim to get better at it.
The patch remains in 'seen' pending further review.