<?xml version='1.0' encoding='utf-8' ?>
<rss version='2.0'>
<channel>
	<title>neilpahl.com Logs Feed: Version Control</title>
	<link></link>
	<description></description>
	<pubDate>Thu, 22 Jul 21 07:39:02 -0400</pubDate>
	<ttl>60</ttl>
	<item>
		<title>Version Control:: Entry 2: Snippets From A Great Git Branching Model</title>
		<description><![CDATA[A great git branching model was proposed on nvie.com and can be found here:http://nvie.com/posts/a-successful-git-branching-model/I highly recommend anyone to first go and read it since it is very elegantly explained, along with pleasant diagrams. Here, I'm just going to highlight a few of the code snippets for my own reference.A] Main Branches- There are 2 main branches... develop and master.- Master is assumed to be production ready, develop is branched from master and merged back to master when it is stable enough.- Master is tagged with a version each time it is updated.Using my private repo that I set up in my last entry, I'll switch to the master branch(probably already starts there but I'll be explicit), then tag my first version of mastergit checkout origin master
git tag -a '0.01' -m 'first version 0.01'
next, I would create and checkout a dev branchgit checkout -b develop masterwhich is just short forgit branch develop master
git checkout developso, if you don't need to checkout develop,]]></description>
		<pubDate>Fri, 29 Jun 12 09:56:01 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/software-development/version-control/2-snippets-from-a-great-git-branching-model/</link>
	</item>
	<item>
		<title>Version Control:: Entry 1: Serving a Private Git Repo With Sharing</title>
		<description><![CDATA[This is pretty much a sumary of what was already said at ...http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server... plus a few customizations and a suggested method of how to init a bare git repo for a user that is restricted by git-shell.Step 1)Install Git server:sudo apt-get install git-server
after installing git-server create a user account which will own the shared repo. Usually just using 'git' is ok, but if you are serving to different organizations, then you would liek to give them their own username so that they cannot access all the other projects ( I would prefix their username with git so that I can recognize why that user is on my system... something like gitjsdesign). If you're on a shared server or cloud, you can protect the data by encrypting their home folder... using (in Ubuntu at least)..adduser --encrypt-home gitjsdesignwithout encryption, you can use:adduser gitjsdesignstep 2)ask gitjsdesign to use ssh and create a public key which they can send(email) you.]]></description>
		<pubDate>Fri, 29 Jun 12 01:32:52 -0400</pubDate>
		<link>http://archived.neilpahl.com/logs/software-development/version-control/1-creating-a-private-git-repo-with-sharing/</link>
	</item>
</channel>
</rss>