<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Windows on The Lone C++ Coder's Blog</title><link>https://www.lonecpluspluscoder.com/tags/microsoft-windows/</link><description>Recent content in Microsoft Windows on The Lone C++ Coder's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 14 Dec 2014 21:39:41 +0000</lastBuildDate><atom:link href="https://www.lonecpluspluscoder.com/tags/microsoft-windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Making git work better on Windows</title><link>https://www.lonecpluspluscoder.com/2014/12/14/making-git-work-better-windows/</link><pubDate>Sun, 14 Dec 2014 21:39:41 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2014/12/14/making-git-work-better-windows/</guid><description>&lt;p>In a &lt;a href="https://www.lonecpluspluscoder.com/2014/03/12/improving-the-performance-of-git-for-windows/" title="Improving the performance of Git for Windows">previous blog post&lt;/a> I explained how you can substantially improve the performance of git on Windows updating the underlying SSH implementation. This performance improvement is very worthwhile in a standard Unix-style git setup where access to the git repository is done using ssh as the transport layer. For a regular development workstation, this update works fine as long as you keep remembering that you need to check and possibly update the ssh binaries after every git update.&lt;/p></description></item></channel></rss>