<?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://azure.microsoft.com/sv-se/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/?WT.mc_id=-twitter-scottha"/>
	<rdf:li rdf:resource="http://www.git-tower.com/blog/version-control-best-practices/"/>
	<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/git-is-not-a-new-subversion/"/>
	<rdf:li rdf:resource="http://ejohn.org/blog/keeping-passwords-in-source-control/"/>
	<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://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="http://guides.beanstalkapp.com/"/>
	<rdf:li rdf:resource="http://www.eecs.harvard.edu/~cduan/technical/git/"/>
	<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://azure.microsoft.com/sv-se/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/?WT.mc_id=-twitter-scottha">
    <title>Announcing Azure Pipelines with unlimited CI/CD minutes for open source | Blogg | Microsoft Azure</title>
    <dc:date>2018-09-11T10:35:37+00:00</dc:date>
    <link>https://azure.microsoft.com/sv-se/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/?WT.mc_id=-twitter-scottha</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[With the introduction of Azure DevOps today, we’re offering developers a new CI/CD service called Azure Pipelines that enables you to continuously build, test, and deploy to any platform or cloud. It has cloud-hosted agents for Linux, macOS, and Windows, powerful workflows with native container support, and flexible deployments to Kubernetes, VMs, and serverless environments.

Microsoft is committed to fueling open source software development. Our next step in this journey is to provide the best CI/CD experience for open source projects. Starting today, Azure Pipelines provides unlimited CI/CD minutes and 10 parallel jobs to every open source project for free. All open source projects run on the same infrastructure that our paying customers use. That means you’ll have the same fast performance and high quality of service. Many of the top open source projects are already using Azure Pipelines for CI/CD, such as Atom, CPython, Pipenv, Tox, Visual Studio Code, and TypeScript – and the list is growing every day.]]></description>
<dc:subject>programming development github opensource versioncontrol testing webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:8420955eb053/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<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:versioncontrol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</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="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/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://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://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="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://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://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>