Google is unable to read the page via the short link to the answer. On first sight, the headers appear to be identical to the question short link. For the question Server Fault responds:
HTTP/1.1 301 Moved Permanently
Location: /questions/199569/where-to-maintain-central-source-repository
...but for the answer:
HTTP/1.1 301 Moved Permanently
Location: /questions/13267/git-and-mercurial/343603#343603
The only real difference is the #fragment in the redirect URL. Also, when using bit.ly URLs to test redirection with and without such fragment, Google gives the same results. So it's a Google thing.
As an aside, note that any Google tool that requests the page chokes on the short link - http://serverfault.com/a/199572:
Rich Snippets Testing Tool:
Google mobile viewer:
No good answer from Google as to why. They say it could be 'caused by an issue with web server configuration, an issue with your hosting provider or even an issue with their ISP'. Might take a question on Meta Stack Overflow to resolve?
--
Update: filed as a bug on Meta.SO.
--
Update: resolved on Google's side.
There is nothing at the moment that will accomplish this properly (it may be possible through some script automation) as Google+ API is currently read only.
Note: The Google+ API currently provides read-only access to public data. All API calls require either an OAuth 2.0 token or an API key.
Maybe the reverse is possible if Blogger allows it. It sounds like something Google might be planning to do. See Use your Google+ profile with your Blogger blogs
Best Answer
On https://plus.google.com/settings, look for the following setting in the "stream" section.