<?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 (Aetles)</title>
    <link>https://pinboard.in/u:Aetles/public/</link>
    <description>recent bookmarks from Aetles</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://fork.dev/"/>
	<rdf:li rdf:resource="https://gitea.io/en-US/"/>
	<rdf:li rdf:resource="https://www.oderland.se/support/artikel/hur-anvander-jag-git-for-att-skapa-en-staging-miljo/"/>
	<rdf:li rdf:resource="http://ohshitgit.com/"/>
	<rdf:li rdf:resource="https://help.github.com/articles/syncing-a-fork/"/>
	<rdf:li rdf:resource="https://rhonabwy.com/2016/04/04/how-to-maintain-a-git-remote-fork/"/>
	<rdf:li rdf:resource="http://www.git-tower.com/blog/version-control-best-practices/"/>
	<rdf:li rdf:resource="https://github.com/blog/2019-how-to-undo-almost-anything-with-git"/>
	<rdf:li rdf:resource="https://about.gitlab.com/"/>
	<rdf:li rdf:resource="http://www.git-tower.com/learn/ebook/command-line/introduction"/>
	<rdf:li rdf:resource="http://smallhadroncollider.svbtle.com/easily-merge-compiled-css-files"/>
	<rdf:li rdf:resource="http://sethrobertson.github.io/GitFixUm/fixup.html"/>
	<rdf:li rdf:resource="http://www.git-tower.com/blog/make-git-rebase-safe-on-osx/"/>
	<rdf:li rdf:resource="http://www.git-tower.com/blog/git-is-not-a-new-subversion/"/>
	<rdf:li rdf:resource="http://ejohn.org/blog/keeping-passwords-in-source-control/"/>
	<rdf:li rdf:resource="http://www.sbf5.com/~cduan/technical/git/"/>
	<rdf:li rdf:resource="http://blog.sourcetreeapp.com/2012/08/21/merge-or-rebase/"/>
	<rdf:li rdf:resource="http://think-like-a-git.net/"/>
	<rdf:li rdf:resource="http://drupaldork.com/2012/04/intro-github-pull-requests"/>
	<rdf:li rdf:resource="https://github.com/highgroove/git_tracker"/>
	<rdf:li rdf:resource="http://guillaume.vanderest.org/2012/01/untracking-files-in-git-and-ignoring-them/"/>
	<rdf:li rdf:resource="http://www.designhammer.com/blog/workflow-and-tools-developing-install-profiles-and-drush-make"/>
	<rdf:li rdf:resource="http://apprikos.se/2011/12/introduktion-till-git"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/455698/best-visual-client-for-git-on-mac-os-x?answertab=active#tab-top"/>
	<rdf:li rdf:resource="https://github.com/rwilcox/git.bbpackage"/>
	<rdf:li rdf:resource="http://thinkvitamin.com/code/source-control/git/our-simple-git-workflow/"/>
	<rdf:li rdf:resource="http://guides.beanstalkapp.com/"/>
	<rdf:li rdf:resource="http://randyfay.com/node/102"/>
	<rdf:li rdf:resource="http://nvie.com/posts/a-successful-git-branching-model/"/>
	<rdf:li rdf:resource="http://www.lullabot.com/articles/git-best-practices-upgrading-patch-process?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+lullabot%2Fplanet-feed+%28Lullabot.com+Drupal+News%29"/>
	<rdf:li rdf:resource="http://deploy.phpfog.com/"/>
	<rdf:li rdf:resource="http://gitx.laullon.com/"/>
	<rdf:li rdf:resource="http://www.eecs.harvard.edu/~cduan/technical/git/"/>
	<rdf:li rdf:resource="http://gitimmersion.com/"/>
	<rdf:li rdf:resource="http://soenkerohde.com/2010/01/connecting-pivotal-tracker-with-github/"/>
	<rdf:li rdf:resource="http://blog.iwalt.com/2010/06/using-bbedits-bbdiff-with-git.html"/>
	<rdf:li rdf:resource="http://randyfay.com/node/83"/>
	<rdf:li rdf:resource="http://www.spheredev.org/wiki/Git_for_the_lazy"/>
	<rdf:li rdf:resource="http://blog.extracheese.org/2010/05/why-i-switched-to-git-from-mercurial.html"/>
	<rdf:li rdf:resource="http://texagon.blogspot.com/2008/02/use-mercurial-you-git.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://fork.dev/">
    <title>Fork - a fast and friendly git client for Mac and Windows</title>
    <dc:date>2019-08-30T11:55:22+00:00</dc:date>
    <link>https://fork.dev/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[a fast and friendly git client for Mac and Windows]]></description>
<dc:subject>git mac osx development programming versioncontrol github</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:3580c6b7d9b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gitea.io/en-US/">
    <title>Gitea</title>
    <dc:date>2018-06-10T16:08:37+00:00</dc:date>
    <link>https://gitea.io/en-US/</link>
    <dc:creator>Aetles</dc:creator><dc:subject>git github opensource self-hosted</dc:subject>
<dc:identifier>https://pinboard.in/u:Aetles/b:ea38d4b21c6d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:self-hosted"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.oderland.se/support/artikel/hur-anvander-jag-git-for-att-skapa-en-staging-miljo/">
    <title>Hur använder jag Git för att skapa en staging-miljö? – Oderland Support</title>
    <dc:date>2017-10-23T08:50:27+00:00</dc:date>
    <link>https://www.oderland.se/support/artikel/hur-anvander-jag-git-for-att-skapa-en-staging-miljo/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Git är till för att underlätta utveckling av kod, framförallt i grupp. Men det kan även användas för andra saker. Ett av dessa användningsområden är för att skapa en staging-miljö där du kan enkelt arbeta och testköra saker på en dev-site för att sedan lansera det live när du är redo.]]></description>
<dc:subject>git oderland webdevelopment webhosting development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:0e00e37e957d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:oderland"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webhosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ohshitgit.com/">
    <title>Oh, shit, git!</title>
    <dc:date>2016-09-10T20:27:47+00:00</dc:date>
    <link>http://ohshitgit.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Git is hard: screwing up is easy, and figuring out how to fix your mistakes is fucking impossible. Git documentation has this chicken and egg problem where you can't search for how to get yourself out of a mess, unless you already know the name of the thing you need to know about in order to fix your problem.

So here are some bad situations I've gotten myself into, and how I eventually got myself out of them in plain english.]]></description>
<dc:subject>git development programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:a4d32b6eb983/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://help.github.com/articles/syncing-a-fork/">
    <title>Syncing a fork - User Documentation</title>
    <dc:date>2016-05-02T10:21:26+00:00</dc:date>
    <link>https://help.github.com/articles/syncing-a-fork/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Sync a fork of a repository to keep it up-to-date with the upstream repository.]]></description>
<dc:subject>git github sync webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:618dbbc78091/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sync"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://rhonabwy.com/2016/04/04/how-to-maintain-a-git-remote-fork/">
    <title>How to maintain a git remote fork | Rhonabwy</title>
    <dc:date>2016-04-05T10:09:29+00:00</dc:date>
    <link>https://rhonabwy.com/2016/04/04/how-to-maintain-a-git-remote-fork/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[In the world of open source software, you make a fork of software all the time. Github has made it super easy, and more importantly, it’s how they (and git) have arranged to collaborate on software. This “how to” is for when you decide that you want to maintain your own fork, with changes in addition, or just divergent, from the original project. For most cases, you are going to be much better off submitting back your changes. Be damned sure you need to keep your changes to yourself.

If you want to keep your changes locally and just for yourself, then immediately recognize that you have just taken on “technical debt”. The interest rate for this debt could be high or low. Following the “debt” metaphor, the cost is based on how much activity and change happens in the repository from which you forked and want to take future changes.

I’m writing this article presuming you want or need to keep a fork with “a few changes added”, and you want to keep it otherwise up to date with the changes happening by others in the open source community. ]]></description>
<dc:subject>git programming webdevelopment development tutorials</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:77b6a99ec73d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tutorials"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.git-tower.com/blog/version-control-best-practices/">
    <title>Version Control Best Practices</title>
    <dc:date>2015-11-28T20:47:02+00:00</dc:date>
    <link>http://www.git-tower.com/blog/version-control-best-practices/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Today, version control should be part of every developer’s tool kit. Knowing the basic rules, however, makes it even more useful. We’ve compiled some best practices that help you get the most out of version control with Git.]]></description>
<dc:subject>git versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:a311838f8494/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/blog/2019-how-to-undo-almost-anything-with-git">
    <title>How to undo (almost) anything with Git</title>
    <dc:date>2015-06-11T20:47:26+00:00</dc:date>
    <link>https://github.com/blog/2019-how-to-undo-almost-anything-with-git</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[One of the most useful features of any version control system is the ability to "undo" your mistakes. In Git, "undo" can mean many slightly different things.

When you make a new commit, Git stores a snapshot of your repository at that specific moment in time; later, you can use Git to go back to an earlier version of your project.

In this post, I'm going to take a look at some common scenarios where you might want to "undo" a change you've made and the best way to do it using Git.]]></description>
<dc:subject>development git github tips webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:9e77dcca5b42/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://about.gitlab.com/">
    <title>Create, review and deploy code together | Better than GitHub | GitLab</title>
    <dc:date>2015-04-21T20:51:11+00:00</dc:date>
    <link>https://about.gitlab.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Feature-packed
Batteries included: GitLab includes git repository management, code reviews, an issue tracking and wiki’s and much more. GitLab comes with GitLab CI, a easy to use continuous integration and deployment tool.

Do it together: Discuss issues and plan milestones. Do code reviews and make line comments. Mention your colleagues anywhere. View activity streams of projects or people.

Plays well with others: GitLab has integrations for tons of tools such as Slack, Hipchat, LDAP, JIRA, Jenkins, many types of hooks and a complete API.

Self-hosted, scalable and updated monthly
On Your Servers: Run it on your own infrastructure. Own everything. Or use our free SaaS GitLab.com

Scales Effortlessly: It runs smoothly a tiny server but can and scale to multiple active servers. A single server handles more than 25,000 users.

Updated Monthly: Every month on the 22nd a big upgrade is released and it’ll only take you only 2 minutes to update.

Community-loved, enterprise ready
GitLab Community Edition is completely free to download and it is open source. It is built by a community of more than 700 people.

GitLab Enterprise Edition comes with a subscription and offers deeper LDAP / AD integration, Jira and Jenkins integration and much more.

Subscriptions allow you to use the Enterprise Edition and includes 24/7 emergency support, more information can be found on our pricing page.]]></description>
<dc:subject>code development git opensource webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:c650edf27db1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.git-tower.com/learn/ebook/command-line/introduction">
    <title>Learn Git - Introduction</title>
    <dc:date>2014-04-18T09:12:55+00:00</dc:date>
    <link>http://www.git-tower.com/learn/ebook/command-line/introduction</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A step-by-step course for the complete beginner]]></description>
<dc:subject>development git webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:1e703b5f93da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://smallhadroncollider.svbtle.com/easily-merge-compiled-css-files">
    <title>Avoiding merge conflicts with compiled CSS files using Git</title>
    <dc:date>2014-02-18T21:40:56+00:00</dc:date>
    <link>http://smallhadroncollider.svbtle.com/easily-merge-compiled-css-files</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[When working with SASS and using Git for version control it’s not uncommon to get merge conflicts on the compiled CSS files. If you’re working as part of a team or just branching and merging a lot this can get annoying.

There are two solutions:]]></description>
<dc:subject>git versioncontrol css webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:de042cd1a7e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sethrobertson.github.io/GitFixUm/fixup.html">
    <title>On undoing, fixing, or removing commits in git</title>
    <dc:date>2014-01-20T08:48:35+00:00</dc:date>
    <link>http://sethrobertson.github.io/GitFixUm/fixup.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[This document is an attempt to be a fairly comprehensive guide to recovering from what you did not mean to do when using git. It isn't that git is so complicated that you need a large document to take care or your particular problem, it is more that the set of things that you might have done is so large that different techniques are needed depending on exactly what you have done and what you want to have happen.]]></description>
<dc:subject>git tips versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:df83e12159c3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.git-tower.com/blog/make-git-rebase-safe-on-osx/">
    <title>A Simple Tweak for Making 'git rebase' Safe on OS X</title>
    <dc:date>2013-11-22T23:45:21+00:00</dc:date>
    <link>http://www.git-tower.com/blog/make-git-rebase-safe-on-osx/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Since OS X 10.7 Lion and the introduction of the Auto-Save and Versions features (which automatically records the history of files), some Git commands like “rebase” might fail on Mac OS systems. 

When performing a large rebase with several commits and many changed files, the rebase process can randomly abort, stating that there are uncommitted changes and rebase cannot continue. However, a “git status” does not report any changes.
When aborting the rebase process and re-running it, it will again randomly abort at any commit until (after several retries) it may or may not finally succeed. 

This can lead to a scenario where a commit is accidentally skipped by the developer if he’s not aware of the issue and continues the rebase. The problem has been tracked down to the revisiond daemon of the OS X Versions feature, which detects file changes and seems to somehow alter the file system info of the file, causing a rebase step to fail as it then detects changes. ]]></description>
<dc:subject>git macosx osx development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:918216220bef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:macosx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.git-tower.com/blog/git-is-not-a-new-subversion/">
    <title>Git is Not a New Subversion</title>
    <dc:date>2013-10-20T13:22:45+00:00</dc:date>
    <link>http://www.git-tower.com/blog/git-is-not-a-new-subversion/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Branching

Yes: Git hasn’t invented the concept of “branches”. But it’s the first system that was deliberately built around this concept. Only when branching becomes as fast & easy as it is in Git will you start to use it extensively. And that’s exactly how you should use it: for every new feature, for every bugfix, for every experiment and proof of concept.
Using branches heavily in your development can make you a better programmer like few other habits can. The reason for this is that it helps you keep order in your project - because branches keep different contexts (features, bugfixes, etc.) separate from each other. ]]></description>
<dc:subject>git programming subversion svn versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:c9f3cfc780db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:subversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:svn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ejohn.org/blog/keeping-passwords-in-source-control/">
    <title>John Resig - Keeping Passwords in Source Control</title>
    <dc:date>2013-02-06T21:47:46+00:00</dc:date>
    <link>http://ejohn.org/blog/keeping-passwords-in-source-control/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[It has to deal with the eternal question: How do you store sensitive configuration options (such as usernames, passwords, etc.) in source control? Typically what I’ve done is to just punt on the problem entirely. I create a dummy configuration file, such as conf/sample-settings.json which has the basic structure but none of the details filled out. 

If someone else needed the details I would just email it to them, or some such (not ideal). Especially when it came time to add additional information to the file or make other changes.

The technique I picked up from Craig was to, instead, keep an encrypted version of the configuration file in source control and then provide a means through which the user can encrypt and decrypt that data.]]></description>
<dc:subject>git passwords encryption sourcecontrol versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:20d4fa4b2424/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:passwords"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sourcecontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sbf5.com/~cduan/technical/git/">
    <title>Understanding Git Conceptually</title>
    <dc:date>2013-01-26T10:51:42+00:00</dc:date>
    <link>http://www.sbf5.com/~cduan/technical/git/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[This is a tutorial on the Git version control system.

Git is quickly becoming one of the most popular version control systems in use. There are plenty of tutorials on Git already. How is this one different?

A Story

When I first started using Git, I read plenty of tutorials, as well as the user manual. Though I picked up the basic usage patterns and commands, I never felt like I grasped what was going on “under the hood,” so to speak. Frequently this resulted in cryptic error messages, caused by my random guessing at the right command to use at a given time. These difficulties worsened as I began to need more advanced (and less well documented) features.

After a few months, I started to understand those under-the-hood concepts. Once I did, suddenly everything made sense. I could understand the manual pages and perform all sorts of source control tasks. Everything that seemed so cryptic and obscure now was perfectly clear.

Understanding Git

The conclusion I draw from this is that you can only really use Git if you understand how Git works. Merely memorizing which commands you should run at what times will work in the short run, but it’s only a matter of time before you get stuck or, worse, break something.]]></description>
<dc:subject>development git programming tutorial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:6acded14f334/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tutorial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.sourcetreeapp.com/2012/08/21/merge-or-rebase/">
    <title>Merge or Rebase? – SourceTree by Atlassian</title>
    <dc:date>2012-08-21T13:55:54+00:00</dc:date>
    <link>http://blog.sourcetreeapp.com/2012/08/21/merge-or-rebase/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[As you’re no doubt aware, Git and Mercurial are great at re-integrating divergent lines of development through merging. They have to be, since their design strongly encourages developers to commit changes in parallel in their own distributed environments. Eventually some or all of these commits have to be brought together into a shared graph, and merging and rebasing are two primary ways that let us do that. So which one do you use?]]></description>
<dc:subject>git versioncontrol mercurial development programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:dca6d053b51a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mercurial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://think-like-a-git.net/">
    <title>Home // Think Like (a) Git</title>
    <dc:date>2012-05-14T13:37:34+00:00</dc:date>
    <link>http://think-like-a-git.net/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[GIT SHOULDN'T BE SO HARD TO LEARN.

When you're just getting started, something as straightforward as a merge can be terrifying. It can take a long time to really become comfortable using some of Git's more advanced features. (It took me a year or two.)

Once people achieve some level of Git enlightenment, they tend to make statements of the form 'Git gets a lot easier once you realize X' -- but that doesn't do much for people staring up Git's steep learning curve.

My goal with this site is to help you, Dear Reader, understand what those smug bastards are talking about.]]></description>
<dc:subject>development git programming versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:e82d2f63d41f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drupaldork.com/2012/04/intro-github-pull-requests">
    <title>Intro to Github Pull Requests | Drupal Dork</title>
    <dc:date>2012-04-26T11:33:11+00:00</dc:date>
    <link>http://drupaldork.com/2012/04/intro-github-pull-requests</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[If your company is hosting code in Github, I sure hope you aren't committing directly to master. This quick screencast demonstrates how to use pull requests so that teammates can review code before it gets merged into the master branch.]]></description>
<dc:subject>git github teamwork</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:36b15917b0fe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:teamwork"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/highgroove/git_tracker">
    <title>highgroove/git_tracker</title>
    <dc:date>2012-04-18T21:45:55+00:00</dc:date>
    <link>https://github.com/highgroove/git_tracker</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[GitTracker, or git-tracker, is a Git hook that will scan your current branch name looking for something it recognizes as a Pivotal Tracker story number. If it finds one, it will automagically add it, in the special format, to your commit message.]]></description>
<dc:subject>pivotaltracker git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:1ef90626bfe8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:pivotaltracker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://guillaume.vanderest.org/2012/01/untracking-files-in-git-and-ignoring-them/">
    <title>Untracking Files in Git and Ignoring Them | Guillaume VanderEst</title>
    <dc:date>2012-04-12T11:13:40+00:00</dc:date>
    <link>http://guillaume.vanderest.org/2012/01/untracking-files-in-git-and-ignoring-them/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[I was wondering how to stop tracking files in Git, and actually found a pretty good little article on it at this site.

git rm --cached filename_here
This will remove it from the Git repository’s tracking; however, it will still keep the files intact in the actual folder.  The second step you’d probably want to pair with this is creating a .gitignore file and putting in the path or files you want to ignore!]]></description>
<dc:subject>git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:375515a91cd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.designhammer.com/blog/workflow-and-tools-developing-install-profiles-and-drush-make">
    <title>Workflow and tools for developing with Drupal install profiles and Drush Make | DesignHammer Website Design and Development in North Carolina</title>
    <dc:date>2012-03-02T18:06:31+00:00</dc:date>
    <link>http://www.designhammer.com/blog/workflow-and-tools-developing-install-profiles-and-drush-make</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A few months ago we completed a Drupal 5 to Drupal 7 migration project for a North Carolina museum website. Actually the Drupal 5 site was more of a Frankenstein site; the previous developers had more or less built their own CMS on top of Drupal. Fortunately, the superb Migrate module made writing migration code for this project a snap.
Getting a workflow together, however, was a bit more of a challenge. We had four people working on the project: two developers, a site builder, and a themer.
Because the project was complex and contained a number of different components, we agreed that development would work best with each developer building aspects of the site on their local machine. That way my work in writing migration code would not interfere with our themer's work, nor would it bother someone working on site building.
The key ingredients to a local development first workflow are git, drush, drush_make (now included in Drush 5), installation profiles, and Features.
In this blog post, we'll review some of the workflow and tools we used for development. We'll use a fictitous "MySite" project for our example.]]></description>
<dc:subject>drupal drush git workflow</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:dab08f98eb3e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:drush"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:workflow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://apprikos.se/2011/12/introduktion-till-git">
    <title>Introduktion till Git - Apprikos</title>
    <dc:date>2011-12-02T09:00:56+00:00</dc:date>
    <link>http://apprikos.se/2011/12/introduktion-till-git</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[En bra video för dig som vill lära dig versionshanteringssystemet Git:]]></description>
<dc:subject>git versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:6c5a4becfc22/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/455698/best-visual-client-for-git-on-mac-os-x?answertab=active#tab-top">
    <title>osx - Best visual client for Git on Mac OS X? - Stack Overflow</title>
    <dc:date>2011-11-23T12:54:58+00:00</dc:date>
    <link>http://stackoverflow.com/questions/455698/best-visual-client-for-git-on-mac-os-x?answertab=active#tab-top</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Update 2011-10-07: SourceTree is good enough that it gradually displaced all other git clients. Developer Steve Streeting was productive and responsive, churning out stable improvements. This week, Atlassian (maker of JIRA and other stuff) announced that they had acquired SourceTree (and Steve Streeting). That is probably good news, because it means more resources behind ST. Even better, SourceTree is now free "for a limited time". So now there is really no reason not to get the best git client for Mac.]]></description>
<dc:subject>git mac osx versioncontrol hg mercurial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:5beb1fc9aadc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:hg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mercurial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rwilcox/git.bbpackage">
    <title>rwilcox/git.bbpackage - GitHub</title>
    <dc:date>2011-11-08T15:40:19+00:00</dc:date>
    <link>https://github.com/rwilcox/git.bbpackage</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A BBEdit package to make working with Git easier
The great thing about BBEdit packages in BBEdit 10 is the fact that everything is gathered together in one place. This package contains useful tools for BBEdit & Git.

This package is part "code you can find elsewhere on the internet" (the Git Blame and diff language modules, for example), and new stuff that I just wrote.]]></description>
<dc:subject>git bbedit</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:4da4b72f033c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:bbedit"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thinkvitamin.com/code/source-control/git/our-simple-git-workflow/">
    <title>Our Simple Git Workflow | Think Vitamin</title>
    <dc:date>2011-08-20T21:46:35+00:00</dc:date>
    <link>http://thinkvitamin.com/code/source-control/git/our-simple-git-workflow/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[One thing I hear a lot from teams that aren't using Git yet is that they've checked it out but it feels really complicated. I remember diving into Git at first and feeling overwhelmed, so I can definitely sympathize. There are so many concepts presented, and very often each article you read talks about a different way to use Git to control your source. In this article we'll talk about the workflow that we use here at Carsonified. We like to keep things simple, and hopefully this will help some teams that are thinking about jumping to Git make the switch.]]></description>
<dc:subject>git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:c2e68b945b26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://guides.beanstalkapp.com/">
    <title>Beanstalk Guides — best practices and how-tos on version control, deployments and collaboration</title>
    <dc:date>2011-07-13T22:31:31+00:00</dc:date>
    <link>http://guides.beanstalkapp.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Version Control
Everything you need to get started with Subversion or Git.]]></description>
<dc:subject>development programming vcs git subversion versioncontrol</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:3ca70e430be9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:vcs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:subversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://randyfay.com/node/102">
    <title>Handling the new .gitignore file in D7 and D8 | RandyFay.com</title>
    <dc:date>2011-05-18T11:53:46+00:00</dc:date>
    <link>http://randyfay.com/node/102</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Drupal 7 and Drupal 8 recently added a default (and sensible) .gitignore file to the standard repository, and while this solves some problems, it has also caused some confusion. (issue)

Here's a link to the actual new .gitignore. Essentially, it excludes the sites/default/files and sites/default/settings.php files from git source control.]]></description>
<dc:subject>development drupal git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:eaaa93e04a5c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nvie.com/posts/a-successful-git-branching-model/">
    <title>A successful Git branching model » nvie.com</title>
    <dc:date>2011-04-15T07:59:17+00:00</dc:date>
    <link>http://nvie.com/posts/a-successful-git-branching-model/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[In this post I present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management.]]></description>
<dc:subject>git programming development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:69221eae1caa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.lullabot.com/articles/git-best-practices-upgrading-patch-process?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+lullabot%2Fplanet-feed+%28Lullabot.com+Drupal+News%29">
    <title>Git Best Practices: Upgrading the Patch Process | Lullabot</title>
    <dc:date>2011-04-13T14:46:38+00:00</dc:date>
    <link>http://www.lullabot.com/articles/git-best-practices-upgrading-patch-process?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+lullabot%2Fplanet-feed+%28Lullabot.com+Drupal+News%29</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[For close to a decade, the CVS version control system has been an integral part of every Drupal developer's workflow. Many site builders could get by downloading release versions of Drupal and assorted modules, but using bleeding-edge code, contributing modules, and submitting bug fixes or enhancements to existing projects all meant getting comfortable with CVS. In March of 2011, that all changed: all of the projects hosted on Drupal.org were migrated to the Git version control system! If you're struggling to get your bearings in the new Git world, this article should help with the transition.]]></description>
<dc:subject>drupal git diff patch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:c3e8a0671043/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:diff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:patch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://deploy.phpfog.com/">
    <title>PHP Fog Git Deploy</title>
    <dc:date>2011-03-01T20:40:54+00:00</dc:date>
    <link>http://deploy.phpfog.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[With PHP Fog Deploy you can deploy any git repository anywhere. For free.

You can deploy your existing git repository to

PHP Fog - with existing beta account
Amazon Beanstalk
FTP
SFTP
All you do is give us a password and we give you a git origin that is tied to your preferred deployment.]]></description>
<dc:subject>php git deploy ftp sftp phpfog</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:346bd8c8369c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:deploy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ftp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sftp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:phpfog"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gitx.laullon.com/">
    <title>GitX (L)</title>
    <dc:date>2011-02-27T15:42:35+00:00</dc:date>
    <link>http://gitx.laullon.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[This is my own version of GitX and it meets all my requirements on my day-to-day use of Git on MacOSX.]]></description>
<dc:subject>git gitx mac macosx</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:6add8d139b26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:gitx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:macosx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eecs.harvard.edu/~cduan/technical/git/">
    <title>Understanding Git Conceptually</title>
    <dc:date>2011-02-25T08:52:15+00:00</dc:date>
    <link>http://www.eecs.harvard.edu/~cduan/technical/git/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[This is a tutorial on the Git version control system.

Git is quickly becoming one of the most popular version control systems in use. There are plenty of tutorials on Git already. How is this one different?

A Story

When I first started using Git, I read plenty of tutorials, as well as the user manual. Though I picked up the basic usage patterns and commands, I never felt like I grasped what was going on “under the hood,” so to speak. Frequently this resulted in cryptic error messages, caused by my random guessing at the right command to use at a given time. These difficulties worsened as I began to need more advanced (and less well documented) features.

After a few months, I started to understand those under-the-hood concepts. Once I did, suddenly everything made sense. I could understand the manual pages and perform all sorts of source control tasks. Everything that seemed so cryptic and obscure now was perfectly clear.

Understanding Git

The conclusion I draw from this is that you can only really use Git if you understand how Git works. Merely memorizing which commands you should run at what times will work in the short run, but it’s only a matter of time before you get stuck or, worse, break something.]]></description>
<dc:subject>git programming versioncontrol tutorial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:1ee9403c89b4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tutorial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gitimmersion.com/">
    <title>Git Immersion - Brought to you by EdgeCase</title>
    <dc:date>2011-01-15T19:03:28+00:00</dc:date>
    <link>http://gitimmersion.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Git is a powerful, sophisticated system for distributed version control. Gaining an understanding of its features opens to developers a new and liberating approach to source code management. The surest path to mastering Git is to immerse oneself in its utilities and operations, to experience it first-hand.

Git Immersion is a guided tour that walks through the fundamentals of Git, inspired by the premise that to know a thing is to do it.]]></description>
<dc:subject>git tutorial</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:275113261fba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tutorial"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://soenkerohde.com/2010/01/connecting-pivotal-tracker-with-github/">
    <title>Connecting Pivotal Tracker with GitHub « Sönke Rohde</title>
    <dc:date>2010-11-17T15:06:17+00:00</dc:date>
    <link>http://soenkerohde.com/2010/01/connecting-pivotal-tracker-with-github/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[GitHub with Pivotal Tracker is the killer agile combination.
With the just release Tracker v3 API update it is now easy to connect them.

You only have to configure GitHub Post-Receive Hooks so you can automatically deliver stories/bugs by providing the Tracker ID in the commit statement like: Fixes #TrackerId]]></description>
<dc:subject>git github pivotaltracker</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:77cded7e5bbb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:pivotaltracker"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.iwalt.com/2010/06/using-bbedits-bbdiff-with-git.html">
    <title>Using BBEdit’s bbdiff with Git - WaltPad</title>
    <dc:date>2010-10-13T14:29:30+00:00</dc:date>
    <link>http://blog.iwalt.com/2010/06/using-bbedits-bbdiff-with-git.html</link>
    <dc:creator>Aetles</dc:creator><dc:subject>bbedit git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:a524ac1dc034/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:bbedit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://randyfay.com/node/83">
    <title>Git over an ssh tunnel (like through a firewall or VPN) | RandyFay.com</title>
    <dc:date>2010-10-12T08:52:40+00:00</dc:date>
    <link>http://randyfay.com/node/83</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[It's a treasured geek secret that ssh can tunnel TCP connections like ssh all over the internet. What does that mean? It means that you can access machines and ports from your local machine that you never thought you could, including git repositories that are behind firewalls or inside VPNs.]]></description>
<dc:subject>git ssh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:92232a49f00b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ssh"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.spheredev.org/wiki/Git_for_the_lazy">
    <title>Git for the lazy - Spheriki</title>
    <dc:date>2010-08-17T13:15:20+00:00</dc:date>
    <link>http://www.spheredev.org/wiki/Git_for_the_lazy</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Git is a distributed version control system. No, you don't need to know what that means to use this guide. Think of it as a time machine: Subversion or CVS without the cruft.
If you make a lot of changes, but decided you made a mistake, this will save your butt.
This guide is for people who want to jump to any point in time with their project/game/whatever, and want something to use for themselves.]]></description>
<dc:subject>git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:cace0cbe0d2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.extracheese.org/2010/05/why-i-switched-to-git-from-mercurial.html">
    <title>Why I Switched to Git From Mercurial — Extra Cheese</title>
    <dc:date>2010-05-17T22:40:56+00:00</dc:date>
    <link>http://blog.extracheese.org/2010/05/why-i-switched-to-git-from-mercurial.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[I used Mercurial for three years, but started switching to Git about a year ago. I now grudgingly recommend Git to anyone who intends to be a full-time programmer. Git's interface is bad in many ways, which is the main complaint about it, and it's a legitimate one. It's just an interface, though, and this is a tool you're going to use all day, every day, in a wide variety of situations.

Here are all of the ways that Mercurial has harmed me, or that I've seen it harm others, and the ways in which Git does good where Mercurial does evil:]]></description>
<dc:subject>hg mercurial git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:577226f834e0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:hg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mercurial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://texagon.blogspot.com/2008/02/use-mercurial-you-git.html">
    <title>Technological Wasteland: Use Mercurial, you Git!</title>
    <dc:date>2009-04-18T22:55:13+00:00</dc:date>
    <link>http://texagon.blogspot.com/2008/02/use-mercurial-you-git.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[It's a land rush of revision control, I tell ya! Among the stable of eager candidates for best-loved DVCS, Git and Mercurial seem to be the two tools capturing the most programmer heart-share for now.

Git is admired because Linus Torvalds wrote it, but Mercurial is better because he didn't.
]]></description>
<dc:subject>mercurial git scm versioncontrol</dc:subject>
<dc:identifier>https://pinboard.in/u:Aetles/b:9cc62c7ec6c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mercurial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:scm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:versioncontrol"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>