<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (mlednor)</title>
    <link>https://pinboard.in/u:mlednor/public/</link>
    <description>recent bookmarks from mlednor</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.cardinalpath.com/how-to-use-svnsync-to-create-a-mirror-backup-of-your-subversion-repository/"/>
	<rdf:li rdf:resource="https://www.petefreitag.com/item/665.cfm"/>
	<rdf:li rdf:resource="http://www.sitepoint.com/database-versioning-dbv/"/>
	<rdf:li rdf:resource="https://github.com/cortesi/hippo"/>
	<rdf:li rdf:resource="http://www.troyhunt.com/2011/05/10-commandments-of-good-source-control.html"/>
	<rdf:li rdf:resource="http://andyjeffries.co.uk/articles/25-tips-for-intermediate-git-users"/>
	<rdf:li rdf:resource="http://carsonified.com/blog/web-apps/why-you-should-switch-from-subversion-to-git/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.cardinalpath.com/how-to-use-svnsync-to-create-a-mirror-backup-of-your-subversion-repository/">
    <title>How to use svnsync to mirror your Subversion repository on another server | Cardinal Path Blog</title>
    <dc:date>2018-11-28T12:53:28+00:00</dc:date>
    <link>https://www.cardinalpath.com/how-to-use-svnsync-to-create-a-mirror-backup-of-your-subversion-repository/</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[How to use svnsync to create a mirror backup of your Subversion repository via Instapaper https://ift.tt/2TSLT0M]]></description>
<dc:subject>versioncontrol subversion</dc:subject>
<dc:identifier>https://pinboard.in/u:mlednor/b:142bdb18e295/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:subversion"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.petefreitag.com/item/665.cfm">
    <title>Moving a Subversion Repository to Another Server</title>
    <dc:date>2018-11-21T12:50:53+00:00</dc:date>
    <link>https://www.petefreitag.com/item/665.cfm</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[Moving a subversion repository from one server to another, while still preserving all your version history may seam like a daunting task, but fortunately it's not too difficult.

I recently had to move a subversion (svn) repository to another server. The repository was on a Windows server and had to be moved to a Linux server.]]></description>
<dc:subject>subversion versioncontrol linux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:56fd6f6a32ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:subversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:linux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sitepoint.com/database-versioning-dbv/">
    <title>Database Versioning with DBV</title>
    <dc:date>2014-10-26T09:42:29+00:00</dc:date>
    <link>http://www.sitepoint.com/database-versioning-dbv/</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[It’s good practice to always use a version control system in any of your projects. Be it a side-project in which you are the only developer, or a team project where five or more people are working on it together. But the idea of putting your database into version control isn’t really that widespread. Often times we take the database for granted.

But like the source files in our project, the database is constantly changing too. That’s why we also need a way to track the changes that we have made and easily share it to other members of our team.

In this article we will take a look at DBV, a database version control system written in PHP for MySQL databases so you need to have PHP and MySQL installed before you can use it, along with a web server like Apache or Nginx.

An important note about this software is that it is not a stand-alone database version control system, because it needs a version control system such as Git, Mercurial or SVN for syncing changes with your team.]]></description>
<dc:subject>database php versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:a78db9cc9367/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cortesi/hippo">
    <title>cortesi/hippo · GitHub</title>
    <dc:date>2013-03-29T20:03:32+00:00</dc:date>
    <link>https://github.com/cortesi/hippo</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[Hippo is a thin layer built on top of Git that simplifies managing a host-wide repository of files with metadata (permissions and ownership). Conceptually, Hippo simply serializes metadata before certain Git commands are run, and restores file metadata after others. By default, the host-wide git repository lives in /var/hippo/.git, metadata is tracked in /var/hippo/manifest.]]></description>
<dc:subject>git opensource versioncontrol sysadmin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:fa7f61254dda/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:sysadmin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.troyhunt.com/2011/05/10-commandments-of-good-source-control.html">
    <title>Troy Hunt: The 10 commandments of good source control management</title>
    <dc:date>2011-05-05T14:06:01+00:00</dc:date>
    <link>http://www.troyhunt.com/2011/05/10-commandments-of-good-source-control.html</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[Ah source control, if there’s a more essential tool which indiscriminately spans programming languages without favour, I’m yet to see it. It’s an essential component of how so many of us work; the lifeblood of many development teams, if you like. So why do we often get it so wrong? Why are some of the really core, fundamentals of version control systems often so poorly understood?

I boil it down to 10 practices – or “commandments” if you like – which often break down or are not properly understand to begin with. These are all relevant to version control products of all types and programming languages of all flavours. I’ll pick some examples from Subversion and .NET but they’re broadly applicable to other technologies.]]></description>
<dc:subject>programming versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:cfd458e5dd37/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://andyjeffries.co.uk/articles/25-tips-for-intermediate-git-users">
    <title>25 Tips for Intermediate Git Users : Andy Jeffries : Ruby on Rails, MySQL and jQuery Developer</title>
    <dc:date>2010-12-10T09:53:17+00:00</dc:date>
    <link>http://andyjeffries.co.uk/articles/25-tips-for-intermediate-git-users</link>
    <dc:creator>mlednor</dc:creator><description><![CDATA[I’ve been using git for about 18 months now and thought I knew it pretty well. Then we had Scott Chacon from GitHub over to do some training at LVS, a supplier/developer of betting/gaming software (where I’m currently contracting) and I learnt a ton in the first day.

As someone who’s always felt fairly comfortable in Git, I thought sharing some of the nuggets I learnt with the community might help someone to find an answer without needing to do lots of research.]]></description>
<dc:subject>git howto tips versioncontrol reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:fc9462cced00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://carsonified.com/blog/web-apps/why-you-should-switch-from-subversion-to-git/">
    <title>Why You Should Switch from Subversion to Git | Carsonified</title>
    <dc:date>2009-11-29T21:46:49+00:00</dc:date>
    <link>http://carsonified.com/blog/web-apps/why-you-should-switch-from-subversion-to-git/</link>
    <dc:creator>mlednor</dc:creator><dc:subject>versioncontrol git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:mlednor/b:278462e62d79/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:mlednor/t:git"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>