<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jasode</author><text>&lt;i&gt;&amp;gt;I think this should link directly to Git&amp;#x27;s release notes (e.g. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&lt;/a&gt;), &lt;/i&gt;&lt;p&gt;I disagree about that suggestion because I think it&amp;#x27;s less friendly for the &lt;i&gt;wider more generalized&lt;/i&gt; HN audience.&lt;p&gt;The very 1st sentence of the blog post already has a helpful hyperlink ref for the &lt;i&gt;&amp;quot;released Git 2.33&amp;quot;&lt;/i&gt; that points to the official Git mailing list post.&lt;p&gt;&lt;i&gt;&amp;gt;The open source Git project just &amp;lt;released Git 2.33==&amp;quot;lore.kernel.org...&amp;quot;&amp;gt; with features and bug fixes from over 74 contributors, 19 of them new.&lt;/i&gt;&lt;p&gt;The rationale for why I believe this is better for most &lt;i&gt;casual&lt;/i&gt; readers:&lt;p&gt;- The blog post has extra context and nice illustrations and lets more hardcore readers &lt;i&gt;also discover&lt;/i&gt; the Junio C Hamano&amp;#x27;s mailing list post for Git.&lt;p&gt;- But the reverse direction of information discovery is not as easy... if HN thread submission was the Junio C Hamano email text, there are no (reciprocal) links to the blog post by Github.&lt;p&gt;Sometimes, the urge to avoid posts from &amp;lt;megacorporation&amp;gt; is &lt;i&gt;reader hostile&lt;/i&gt;.&lt;p&gt;ADD EDIT reply to : &lt;i&gt;&amp;gt;OR it can link to the blogpost with a different title.&lt;/i&gt;&lt;p&gt;I thought this was superfluous&amp;#x2F;redundant since &amp;quot;(github.blog)&amp;quot; in parentheses -- is already the composited title of the thread even if the submitter didn&amp;#x27;t put &amp;quot;Github&amp;quot; in the title.&lt;p&gt;&lt;i&gt;&amp;gt;I did not notice an objection to linking to a mega corporation.&lt;/i&gt;&lt;p&gt;It was a general response to 3 comments (so far) I saw that indirectly complained about this thread being a Github blog post instead of something official from a Git maintainer such as a Junio C Hamano email.</text><parent_chain><item><author>chucky</author><text>I think this should link directly to Git&amp;#x27;s release notes (e.g. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&lt;/a&gt;), or the title should be updated to somehow reflect that this is Github&amp;#x27;s blog post about the changes, not Git&amp;#x27;s official announcement.&lt;p&gt;Git is not owned or stewarded by Github, and posts like this  reinforce the common and unfortunate image that it is.</text></item></parent_chain></comment><story><title>Git 2.33</title><url>https://github.blog/2021-08-16-highlights-from-git-2-33/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>remus</author><text>I agree with the principal, but in practice the mailing list post is pretty inscrutable to me (as a casual git user, maybe more experienced users find it more helpful?) On the other hand the github blog post provides a lot of extra context and explanation around the changes which adds a lot of value to me.</text><parent_chain><item><author>chucky</author><text>I think this should link directly to Git&amp;#x27;s release notes (e.g. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lore.kernel.org&amp;#x2F;git&amp;#x2F;xmqq1r6touqi.fsf@gitster.g&amp;#x2F;&lt;/a&gt;), or the title should be updated to somehow reflect that this is Github&amp;#x27;s blog post about the changes, not Git&amp;#x27;s official announcement.&lt;p&gt;Git is not owned or stewarded by Github, and posts like this  reinforce the common and unfortunate image that it is.</text></item></parent_chain></comment><story><title>Git 2.33</title><url>https://github.blog/2021-08-16-highlights-from-git-2-33/</url></story>