<?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 (emilsit)</title>
    <link>https://pinboard.in/u:emilsit/public/</link>
    <description>recent bookmarks from emilsit</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://fourkitchens.com/blog/2009/02/03/importance-atomicity-or-why-git-staging-area-bad"/>
	<rdf:li rdf:resource="http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/"/>
	<rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/37754"/>
	<rdf:li rdf:resource="http://gitster.livejournal.com/27297.html"/>
	<rdf:li rdf:resource="http://madduck.net/blog/2007.10.07:converting-a-package-to-git/"/>
	<rdf:li rdf:resource="http://madduck.net/blog/2007.10.03:packaging-with-git/"/>
	<rdf:li rdf:resource="http://gitster.livejournal.com/26540.html"/>
	<rdf:li rdf:resource="http://kerneltrap.org/Linux/Git_Management"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://fourkitchens.com/blog/2009/02/03/importance-atomicity-or-why-git-staging-area-bad">
    <title>Enforcing branch commit atomicity (or, why the git staging area is bad) | Four Kitchens</title>
    <dc:date>2009-02-04T16:20:02+00:00</dc:date>
    <link>http://fourkitchens.com/blog/2009/02/03/importance-atomicity-or-why-git-staging-area-bad</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA["Committing in git with only some changes added to the staging area still results in an "atomic" revision that may never have existed as a working copy and may not work." -- that is, git (and darcs and bzr unshelve) require that the developer is careful to really test the commits he has, before pushing.  Author argues that bzr is better, but there's interesting discussion in comments too.
]]></description>
<dc:subject>git bzr ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:173c206ce3b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:bzr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/">
    <title>Dr Nic » Migrating project websites to github pages with sake tasks, new websites with jekyll_generator</title>
    <dc:date>2009-02-04T02:08:07+00:00</dc:date>
    <link>http://drnicwilliams.com/2008/12/21/migrating-project-websites-to-github-pages-with-sake-tasks-new-websites-with-jekyll_generator/</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[Tutorial on how to migrate a website into github pages---github requires your website on a special branch, so here's a pointer to some magic that takes a directory, turns it into a special branch, and then "mounts" it as a submodule.
]]></description>
<dc:subject>git github ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:b6986df12de2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/37754">
    <title>Question about fsck-objects output</title>
    <dc:date>2009-02-02T14:34:13+00:00</dc:date>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/37754</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[Linus on the meaning of git-fsck output, how to fix it---if necessary---and when *not* to fix it.  (Now part of the git documentation.)
]]></description>
<dc:subject>git ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:c5793b60dbe5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gitster.livejournal.com/27297.html">
    <title>gitster's journal - Resolving conflicts/dependencies between topic branches early</title>
    <dc:date>2009-02-02T00:18:20+00:00</dc:date>
    <link>http://gitster.livejournal.com/27297.html</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[Junio on how to maintain topic branches, bug fixes, and a workflow to avoid missing related fixes when merging between branches.
]]></description>
<dc:subject>git workflow ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:91cbd37693ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://madduck.net/blog/2007.10.07:converting-a-package-to-git/">
    <title>Converting a package to Git</title>
    <dc:date>2009-01-25T10:48:35+00:00</dc:date>
    <link>http://madduck.net/blog/2007.10.07:converting-a-package-to-git/</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[Martin Krafft explains how to do a clean git-svn import, rebase a git history on top of it, and convert patches to branches; with commands you can copy-paste.  Plus a short bonus lesson on merging.  In a Debian packaging context but still useful elsewhere.
]]></description>
<dc:subject>svn git-svn reference ff:git-world subversion git workflow</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:abff38b2f34e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:svn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git-svn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:subversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:workflow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://madduck.net/blog/2007.10.03:packaging-with-git/">
    <title>Packaging with Git</title>
    <dc:date>2009-01-25T10:39:20+00:00</dc:date>
    <link>http://madduck.net/blog/2007.10.03:packaging-with-git/</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[A very detailed walkthrough from Martin Krafft on how to maintain a Debian package in git, tracking a git upstream.  Includes discussion of branch usage showing examples for topics and integration, with commands you can run.  Also the use of tags.  Useful even for non-Debian work!  From 2007; some git commands may have changed.
]]></description>
<dc:subject>git packaging workflow reference ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:2afc77f84c77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:packaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gitster.livejournal.com/26540.html">
    <title>gitster's journal - Never merging back</title>
    <dc:date>2009-01-24T17:08:08+00:00</dc:date>
    <link>http://gitster.livejournal.com/26540.html</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[Nice article on how to manage branches that have some changes that need to get merged back to master, and some that don't.  These can be release branches or they can be branches targeted at specific customers.
]]></description>
<dc:subject>git workflow ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:9d39397b2df0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kerneltrap.org/Linux/Git_Management">
    <title>Git Management | KernelTrap</title>
    <dc:date>2008-07-09T23:29:01+00:00</dc:date>
    <link>http://kerneltrap.org/Linux/Git_Management</link>
    <dc:creator>emilsit</dc:creator><description><![CDATA[How to use "git rebase" with topic branches and the relative workflows used by leaf-developers versus subsystem maintainers and core integrators.  The thoughts of Linus himself.
]]></description>
<dc:subject>git workflow ff:git-world</dc:subject>
<dc:identifier>https://pinboard.in/u:emilsit/b:a96587a78ad9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:emilsit/t:ff:git-world"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>