<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>git on Lazy Malloc</title>
    <link>http://www.lazymalloc.com/tags/git/</link>
    <description>Recent content in git on Lazy Malloc</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright (c) 2017-2022 Lazy Malloc authors.</copyright>
    <lastBuildDate>Sun, 01 Oct 2017 21:36:01 -0500</lastBuildDate><atom:link href="http://www.lazymalloc.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Multiple Working Directories in both Mercurial and Git</title>
      <link>http://www.lazymalloc.com/posts/2017/multiple-working-directories-in-hg-git/</link>
      <pubDate>Sun, 01 Oct 2017 21:36:01 -0500</pubDate>
      
      <guid>http://www.lazymalloc.com/posts/2017/multiple-working-directories-in-hg-git/</guid>
      <description>&lt;p&gt;I’ve been told that utilizing this functionality is terrible, bad practice, a
mistake, contributes to climate change, etc. However, it fits into my workflow
pretty well, and it might fit into yours as well. After all, it is implemented
in at least two version control systems&amp;hellip;so some people must find it useful,
right?&lt;/p&gt;
&lt;p&gt;I use both Mercurial and Git depending on the project, so I’ll briefly describe
the usage for both, with references to more complete documentation at the end.
While the implementation is different, in both cases there are essentially
multiple working directories for a single repository.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
