{"thread":{"id":"31398","subject":"rev-parse -q --verify with not existent upstream branch","startedAt":"2012-08-31T17:11:58Z","lastAt":"2012-08-31T17:11:58Z","messageCount":1,"participants":["Kacper Kornet"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"198155","messageId":"20120831171158.GM21362@camk.edu.pl","threadId":"31398","inReplyTo":null,"subject":"rev-parse -q --verify with not existent upstream branch","fromName":"Kacper Kornet","fromEmail":"draenog@pld-linux.org","sentAt":"2012-08-31T17:11:58Z","receivedAt":"2012-08-31T17:11:58Z","isPatch":false,"sender":{"key":"draenog@pld-linux.org","avatar":"https://avatars.githubusercontent.com/u/608762?v=4"},"body":"\nDocumentation to git-rev-parse claims that\n\n-q, --quiet\n   Only meaningful in --verify mode. Do not output an error\n   message if the first argument is not a valid object name; instead exit\n   with non-zero status silently.\n\n\nHowever when I try to check if the current branch has a configured\nupstream one with:\n\ngit rev-parse -q --verify  '@{u}'\n\nI still receives the error message:\n\nerror: No upstream configured for branch 'threading'\n\nAdditinally withour -q --verify options the error message is printed\ntwice:\n\nerror: No upstream configured for branch 'threading'\n@{u}\nerror: No upstream configured for branch 'threading'\nfatal: ambiguous argument '@{u}': unknown revision or path not in the\nworking tree.\nUse '--' to separate paths from revision\n\n-- \n  Kacper\n"}]}