vagrant-host-ruby-provisioner 0.0.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 1a5ad2d271af393d98459f9154588d1b2d81464d
+  data.tar.gz: aa757e28a328fe88a29b8a7dee2ca6878a9e5a41
+SHA512:
+  metadata.gz: 9814878a4f3e9cb734d84dc0de0d980359790247c5b987e53c283c7bd430d53153254a46bb0e770c3ecd8a40bd0e74fd3ff6b11228f2e3641be3f1d8fb8921f2
+  data.tar.gz: de24b2ea27891406d1eed78fe57afdeaf16d916cd95a74029fb0519d749af7c6b14ab25bccddae9497c76bf03856475187211bb5258ad3cd2921e67c9dbd85a0

data/.bundle/install.log

@@ -0,0 +1,12 @@
+# Logfile created on 2014-01-12 02:12:43 -0500 by logger.rb/36483
+I, [2014-01-12T02:12:43.486224 #66589]  INFO -- : 0:  rake (10.1.1) from /Library/Ruby/Gems/2.0.0/specifications/rake-10.1.1.gemspec
+I, [2014-01-12T02:12:43.487473 #66589]  INFO -- : 0:  bundler (1.5.1) from /Library/Ruby/Gems/2.0.0/specifications/bundler-1.5.1.gemspec
+I, [2014-01-12T02:12:43.506166 #66589]  INFO -- : 0:  ffi (1.9.3) from /Library/Ruby/Gems/2.0.0/specifications/ffi-1.9.3.gemspec
+I, [2014-01-12T02:12:43.508075 #66589]  INFO -- : 0:  childprocess (0.3.9) from /Library/Ruby/Gems/2.0.0/specifications/childprocess-0.3.9.gemspec
+I, [2014-01-12T02:12:43.508721 #66589]  INFO -- : 0:  erubis (2.7.0) from /Library/Ruby/Gems/2.0.0/specifications/erubis-2.7.0.gemspec
+I, [2014-01-12T02:12:43.509280 #66589]  INFO -- : 0:  i18n (0.6.9) from /Library/Ruby/Gems/2.0.0/specifications/i18n-0.6.9.gemspec
+I, [2014-01-12T02:12:43.510151 #66589]  INFO -- : 0:  log4r (1.1.10) from /Library/Ruby/Gems/2.0.0/specifications/log4r-1.1.10.gemspec
+I, [2014-01-12T02:12:43.510654 #66589]  INFO -- : 0:  net-ssh (2.7.0) from /Library/Ruby/Gems/2.0.0/specifications/net-ssh-2.7.0.gemspec
+I, [2014-01-12T02:12:43.511157 #66589]  INFO -- : 0:  net-scp (1.1.2) from /Library/Ruby/Gems/2.0.0/specifications/net-scp-1.1.2.gemspec
+I, [2014-01-12T02:12:45.255861 #66589]  INFO -- : 0:  vagrant (1.5.0.dev) from /Library/Ruby/Gems/2.0.0/bundler/gems/vagrant-a241c9ac5940/vagrant.gemspec
+I, [2014-01-12T02:12:45.379457 #66589]  INFO -- : 0:  vagrant-host-ruby-provisioner (0.0.2) from /Users/jonathanmarvens/Projects/software/jebbit/vagrant-ruby-provisioner/vagrant-host-ruby-provisioner.gemspec

data/.git/COMMIT_EDITMSG

@@ -0,0 +1 @@
+You piss me off RubyGems.

data/.git/HEAD

@@ -0,0 +1 @@
+ref: refs/heads/develop

data/.git/ORIG_HEAD

@@ -0,0 +1 @@
+742a7893188658eaea4c183b85395472b3c90a50

data/.git/config

@@ -0,0 +1,27 @@
+[core]
+	repositoryformatversion = 0
+	filemode = true
+	bare = false
+	logallrefupdates = true
+	ignorecase = true
+	precomposeunicode = false
+[gitflow "branch"]
+	master = master
+	develop = develop
+[gitflow "prefix"]
+	feature = feature/
+	release = release/
+	hotfix = hotfix/
+	support = support/
+	versiontag = v
+[user]
+	email = jonathan.barronville@jebbit.com
+[remote "origin"]
+	url = git@github.com:jebbit/vagrant-host-ruby-provisioner.git
+	fetch = +refs/heads/*:refs/remotes/origin/*
+[branch "develop"]
+	remote = origin
+	merge = refs/heads/develop
+[branch "master"]
+	remote = origin
+	merge = refs/heads/master

data/.git/description

@@ -0,0 +1 @@
+Unnamed repository; edit this file 'description' to name the repository.

data/.git/hooks/applypatch-msg.sample

@@ -0,0 +1,15 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message taken by
+# applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.  The hook is
+# allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "applypatch-msg".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/commit-msg" &&
+	exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
+:

data/.git/hooks/commit-msg.sample

@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message.
+# Called by "git commit" with one argument, the name of the file
+# that has the commit message.  The hook should exit with non-zero
+# status after issuing an appropriate message if it wants to stop the
+# commit.  The hook is allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "commit-msg".
+
+# Uncomment the below to add a Signed-off-by line to the message.
+# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
+# hook is more suited to it.
+#
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
+
+# This example catches duplicate Signed-off-by lines.
+
+test "" = "$(grep '^Signed-off-by: ' "$1" |
+	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
+	echo >&2 Duplicate Signed-off-by lines.
+	exit 1
+}

data/.git/hooks/post-update.sample

@@ -0,0 +1,8 @@
+#!/bin/sh
+#
+# An example hook script to prepare a packed repository for use over
+# dumb transports.
+#
+# To enable this hook, rename this file to "post-update".
+
+exec git update-server-info

data/.git/hooks/pre-applypatch.sample

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed
+# by applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-applypatch".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/pre-commit" &&
+	exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"}
+:

data/.git/hooks/pre-commit.sample

@@ -0,0 +1,50 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git commit" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message if
+# it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-commit".
+
+if git rev-parse --verify HEAD >/dev/null 2>&1
+then
+	against=HEAD
+else
+	# Initial commit: diff against an empty tree object
+	against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
+fi
+
+# If you want to allow non-ascii filenames set this variable to true.
+allownonascii=$(git config hooks.allownonascii)
+
+# Redirect output to stderr.
+exec 1>&2
+
+# Cross platform projects tend to avoid non-ascii filenames; prevent
+# them from being added to the repository. We exploit the fact that the
+# printable range starts at the space character and ends with tilde.
+if [ "$allownonascii" != "true" ] &&
+	# Note that the use of brackets around a tr range is ok here, (it's
+	# even required, for portability to Solaris 10's /usr/bin/tr), since
+	# the square bracket bytes happen to fall in the designated range.
+	test $(git diff --cached --name-only --diff-filter=A -z $against |
+	  LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
+then
+	echo "Error: Attempt to add a non-ascii file name."
+	echo
+	echo "This can cause problems if you want to work"
+	echo "with people on other platforms."
+	echo
+	echo "To be portable it is advisable to rename the file ..."
+	echo
+	echo "If you know what you are doing you can disable this"
+	echo "check using:"
+	echo
+	echo "  git config hooks.allownonascii true"
+	echo
+	exit 1
+fi
+
+# If there are whitespace errors, print the offending file names and fail.
+exec git diff-index --check --cached $against --

data/.git/hooks/pre-push.sample

@@ -0,0 +1,53 @@
+#!/bin/sh
+
+# An example hook script to verify what is about to be pushed.  Called by "git
+# push" after it has checked the remote status, but before anything has been
+# pushed.  If this script exits with a non-zero status nothing will be pushed.
+#
+# This hook is called with the following parameters:
+#
+# $1 -- Name of the remote to which the push is being done
+# $2 -- URL to which the push is being done
+#
+# If pushing without using a named remote those arguments will be equal.
+#
+# Information about the commits which are being pushed is supplied as lines to
+# the standard input in the form:
+#
+#   <local ref> <local sha1> <remote ref> <remote sha1>
+#
+# This sample shows how to prevent push of commits where the log message starts
+# with "WIP" (work in progress).
+
+remote="$1"
+url="$2"
+
+z40=0000000000000000000000000000000000000000
+
+IFS=' '
+while read local_ref local_sha remote_ref remote_sha
+do
+	if [ "$local_sha" = $z40 ]
+	then
+		# Handle delete
+	else
+		if [ "$remote_sha" = $z40 ]
+		then
+			# New branch, examine all commits
+			range="$local_sha"
+		else
+			# Update to existing branch, examine new commits
+			range="$remote_sha..$local_sha"
+		fi
+
+		# Check for WIP commit
+		commit=`git rev-list -n 1 --grep '^WIP' "$range"`
+		if [ -n "$commit" ]
+		then
+			echo "Found WIP commit in $local_ref, not pushing"
+			exit 1
+		fi
+	fi
+done
+
+exit 0

data/.git/hooks/pre-rebase.sample

@@ -0,0 +1,169 @@
+#!/bin/sh
+#
+# Copyright (c) 2006, 2008 Junio C Hamano
+#
+# The "pre-rebase" hook is run just before "git rebase" starts doing
+# its job, and can prevent the command from running by exiting with
+# non-zero status.
+#
+# The hook is called with the following parameters:
+#
+# $1 -- the upstream the series was forked from.
+# $2 -- the branch being rebased (or empty when rebasing the current branch).
+#
+# This sample shows how to prevent topic branches that are already
+# merged to 'next' branch from getting rebased, because allowing it
+# would result in rebasing already published history.
+
+publish=next
+basebranch="$1"
+if test "$#" = 2
+then
+	topic="refs/heads/$2"
+else
+	topic=`git symbolic-ref HEAD` ||
+	exit 0 ;# we do not interrupt rebasing detached HEAD
+fi
+
+case "$topic" in
+refs/heads/??/*)
+	;;
+*)
+	exit 0 ;# we do not interrupt others.
+	;;
+esac
+
+# Now we are dealing with a topic branch being rebased
+# on top of master.  Is it OK to rebase it?
+
+# Does the topic really exist?
+git show-ref -q "$topic" || {
+	echo >&2 "No such branch $topic"
+	exit 1
+}
+
+# Is topic fully merged to master?
+not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
+if test -z "$not_in_master"
+then
+	echo >&2 "$topic is fully merged to master; better remove it."
+	exit 1 ;# we could allow it, but there is no point.
+fi
+
+# Is topic ever merged to next?  If so you should not be rebasing it.
+only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
+only_next_2=`git rev-list ^master           ${publish} | sort`
+if test "$only_next_1" = "$only_next_2"
+then
+	not_in_topic=`git rev-list "^$topic" master`
+	if test -z "$not_in_topic"
+	then
+		echo >&2 "$topic is already up-to-date with master"
+		exit 1 ;# we could allow it, but there is no point.
+	else
+		exit 0
+	fi
+else
+	not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
+	/usr/bin/perl -e '
+		my $topic = $ARGV[0];
+		my $msg = "* $topic has commits already merged to public branch:\n";
+		my (%not_in_next) = map {
+			/^([0-9a-f]+) /;
+			($1 => 1);
+		} split(/\n/, $ARGV[1]);
+		for my $elem (map {
+				/^([0-9a-f]+) (.*)$/;
+				[$1 => $2];
+			} split(/\n/, $ARGV[2])) {
+			if (!exists $not_in_next{$elem->[0]}) {
+				if ($msg) {
+					print STDERR $msg;
+					undef $msg;
+				}
+				print STDERR " $elem->[1]\n";
+			}
+		}
+	' "$topic" "$not_in_next" "$not_in_master"
+	exit 1
+fi
+
+exit 0
+
+################################################################
+
+This sample hook safeguards topic branches that have been
+published from being rewound.
+
+The workflow assumed here is:
+
+ * Once a topic branch forks from "master", "master" is never
+   merged into it again (either directly or indirectly).
+
+ * Once a topic branch is fully cooked and merged into "master",
+   it is deleted.  If you need to build on top of it to correct
+   earlier mistakes, a new topic branch is created by forking at
+   the tip of the "master".  This is not strictly necessary, but
+   it makes it easier to keep your history simple.
+
+ * Whenever you need to test or publish your changes to topic
+   branches, merge them into "next" branch.
+
+The script, being an example, hardcodes the publish branch name
+to be "next", but it is trivial to make it configurable via
+$GIT_DIR/config mechanism.
+
+With this workflow, you would want to know:
+
+(1) ... if a topic branch has ever been merged to "next".  Young
+    topic branches can have stupid mistakes you would rather
+    clean up before publishing, and things that have not been
+    merged into other branches can be easily rebased without
+    affecting other people.  But once it is published, you would
+    not want to rewind it.
+
+(2) ... if a topic branch has been fully merged to "master".
+    Then you can delete it.  More importantly, you should not
+    build on top of it -- other people may already want to
+    change things related to the topic as patches against your
+    "master", so if you need further changes, it is better to
+    fork the topic (perhaps with the same name) afresh from the
+    tip of "master".
+
+Let's look at this example:
+
+		   o---o---o---o---o---o---o---o---o---o "next"
+		  /       /           /           /
+		 /   a---a---b A     /           /
+		/   /               /           /
+	       /   /   c---c---c---c B         /
+	      /   /   /             \         /
+	     /   /   /   b---b C     \       /
+	    /   /   /   /             \     /
+    ---o---o---o---o---o---o---o---o---o---o---o "master"
+
+
+A, B and C are topic branches.
+
+ * A has one fix since it was merged up to "next".
+
+ * B has finished.  It has been fully merged up to "master" and "next",
+   and is ready to be deleted.
+
+ * C has not merged to "next" at all.
+
+We would want to allow C to be rebased, refuse A, and encourage
+B to be deleted.
+
+To compute (1):
+
+	git rev-list ^master ^topic next
+	git rev-list ^master        next
+
+	if these match, topic has not merged in next at all.
+
+To compute (2):
+
+	git rev-list master..topic
+
+	if this is empty, it is fully merged to "master".

data/.git/hooks/prepare-commit-msg.sample

@@ -0,0 +1,36 @@
+#!/bin/sh
+#
+# An example hook script to prepare the commit log message.
+# Called by "git commit" with the name of the file that has the
+# commit message, followed by the description of the commit
+# message's source.  The hook's purpose is to edit the commit
+# message file.  If the hook fails with a non-zero status,
+# the commit is aborted.
+#
+# To enable this hook, rename this file to "prepare-commit-msg".
+
+# This hook includes three examples.  The first comments out the
+# "Conflicts:" part of a merge commit.
+#
+# The second includes the output of "git diff --name-status -r"
+# into the message, just before the "git status" output.  It is
+# commented because it doesn't cope with --amend or with squashed
+# commits.
+#
+# The third example adds a Signed-off-by line to the message, that can
+# still be edited.  This is rarely a good idea.
+
+case "$2,$3" in
+  merge,)
+    /usr/bin/perl -i.bak -ne 's/^/# /, s/^# #/#/ if /^Conflicts/ .. /#/; print' "$1" ;;
+
+# ,|template,)
+#   /usr/bin/perl -i.bak -pe '
+#      print "\n" . `git diff --cached --name-status -r`
+#	 if /^#/ && $first++ == 0' "$1" ;;
+
+  *) ;;
+esac
+
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"

data/.git/hooks/update.sample

@@ -0,0 +1,128 @@
+#!/bin/sh
+#
+# An example hook script to blocks unannotated tags from entering.
+# Called by "git receive-pack" with arguments: refname sha1-old sha1-new
+#
+# To enable this hook, rename this file to "update".
+#
+# Config
+# ------
+# hooks.allowunannotated
+#   This boolean sets whether unannotated tags will be allowed into the
+#   repository.  By default they won't be.
+# hooks.allowdeletetag
+#   This boolean sets whether deleting tags will be allowed in the
+#   repository.  By default they won't be.
+# hooks.allowmodifytag
+#   This boolean sets whether a tag may be modified after creation. By default
+#   it won't be.
+# hooks.allowdeletebranch
+#   This boolean sets whether deleting branches will be allowed in the
+#   repository.  By default they won't be.
+# hooks.denycreatebranch
+#   This boolean sets whether remotely creating branches will be denied
+#   in the repository.  By default this is allowed.
+#
+
+# --- Command line
+refname="$1"
+oldrev="$2"
+newrev="$3"
+
+# --- Safety check
+if [ -z "$GIT_DIR" ]; then
+	echo "Don't run this script from the command line." >&2
+	echo " (if you want, you could supply GIT_DIR then run" >&2
+	echo "  $0 <ref> <oldrev> <newrev>)" >&2
+	exit 1
+fi
+
+if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
+	echo "usage: $0 <ref> <oldrev> <newrev>" >&2
+	exit 1
+fi
+
+# --- Config
+allowunannotated=$(git config --bool hooks.allowunannotated)
+allowdeletebranch=$(git config --bool hooks.allowdeletebranch)
+denycreatebranch=$(git config --bool hooks.denycreatebranch)
+allowdeletetag=$(git config --bool hooks.allowdeletetag)
+allowmodifytag=$(git config --bool hooks.allowmodifytag)
+
+# check for no description
+projectdesc=$(sed -e '1q' "$GIT_DIR/description")
+case "$projectdesc" in
+"Unnamed repository"* | "")
+	echo "*** Project description file hasn't been set" >&2
+	exit 1
+	;;
+esac
+
+# --- Check types
+# if $newrev is 0000...0000, it's a commit to delete a ref.
+zero="0000000000000000000000000000000000000000"
+if [ "$newrev" = "$zero" ]; then
+	newrev_type=delete
+else
+	newrev_type=$(git cat-file -t $newrev)
+fi
+
+case "$refname","$newrev_type" in
+	refs/tags/*,commit)
+		# un-annotated tag
+		short_refname=${refname##refs/tags/}
+		if [ "$allowunannotated" != "true" ]; then
+			echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2
+			echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2
+			exit 1
+		fi
+		;;
+	refs/tags/*,delete)
+		# delete tag
+		if [ "$allowdeletetag" != "true" ]; then
+			echo "*** Deleting a tag is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/tags/*,tag)
+		# annotated tag
+		if [ "$allowmodifytag" != "true" ] && git rev-parse $refname > /dev/null 2>&1
+		then
+			echo "*** Tag '$refname' already exists." >&2
+			echo "*** Modifying a tag is not allowed in this repository." >&2
+			exit 1
+		fi
+		;;
+	refs/heads/*,commit)
+		# branch
+		if [ "$oldrev" = "$zero" -a "$denycreatebranch" = "true" ]; then
+			echo "*** Creating a branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/heads/*,delete)
+		# delete branch
+		if [ "$allowdeletebranch" != "true" ]; then
+			echo "*** Deleting a branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/remotes/*,commit)
+		# tracking branch
+		;;
+	refs/remotes/*,delete)
+		# delete tracking branch
+		if [ "$allowdeletebranch" != "true" ]; then
+			echo "*** Deleting a tracking branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	*)
+		# Anything else (is there anything else?)
+		echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2
+		exit 1
+		;;
+esac
+
+# --- Finished
+exit 0

data/.git/info/exclude

@@ -0,0 +1,7 @@
+# git ls-files --others --exclude-from=.git/info/exclude
+# Lines that start with '#' are comments.
+# For a project mostly in C, the following would be a good set of
+# exclude patterns (uncomment them if you want to use them):
+# *.[oa]
+# *~
+.DS_Store

data/.git/logs/HEAD

@@ -0,0 +1,18 @@
+0000000000000000000000000000000000000000 cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 Jonathan Barronville <jonathan@belairlabs.com> 1389508799 -0500	commit (initial): Initial commit
+cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 Jonathan Barronville <jonathan@belairlabs.com> 1389508800 -0500	checkout: moving from master to develop
+cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508829 -0500	commit: First legit commit with all the code.
+ad48deb220c14f264ea31ae345163f53434a4a89 ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508838 -0500	checkout: moving from develop to release/0.0.1
+ad48deb220c14f264ea31ae345163f53434a4a89 cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508846 -0500	checkout: moving from release/0.0.1 to master
+cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 dfa83063026d1177200981794e135a1e8843e56a Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508846 -0500	merge release/0.0.1: Merge made by the 'recursive' strategy.
+dfa83063026d1177200981794e135a1e8843e56a ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508859 -0500	checkout: moving from master to develop
+ad48deb220c14f264ea31ae345163f53434a4a89 dfa83063026d1177200981794e135a1e8843e56a Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510156 -0500	checkout: moving from develop to hotfix/0.0.1-hotfix-small-update-001
+dfa83063026d1177200981794e135a1e8843e56a a03c75b8391d082613b8e060afc753d8e344e033 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510211 -0500	commit: Small updates.
+a03c75b8391d082613b8e060afc753d8e344e033 dfa83063026d1177200981794e135a1e8843e56a Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510236 -0500	checkout: moving from hotfix/0.0.1-hotfix-small-update-001 to master
+dfa83063026d1177200981794e135a1e8843e56a 742a7893188658eaea4c183b85395472b3c90a50 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510236 -0500	merge hotfix/0.0.1-hotfix-small-update-001: Merge made by the 'recursive' strategy.
+742a7893188658eaea4c183b85395472b3c90a50 ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510245 -0500	checkout: moving from master to develop
+ad48deb220c14f264ea31ae345163f53434a4a89 3053454fe8ce25790fb0bb99e085aed05f0920c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510245 -0500	merge hotfix/0.0.1-hotfix-small-update-001: Merge made by the 'recursive' strategy.
+3053454fe8ce25790fb0bb99e085aed05f0920c9 805263aed3f51ee4f45aa2dfe70f8375c76900c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510694 -0500	commit: You piss me off RubyGems.
+805263aed3f51ee4f45aa2dfe70f8375c76900c9 805263aed3f51ee4f45aa2dfe70f8375c76900c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510715 -0500	checkout: moving from develop to release/0.0.2
+805263aed3f51ee4f45aa2dfe70f8375c76900c9 742a7893188658eaea4c183b85395472b3c90a50 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510717 -0500	checkout: moving from release/0.0.2 to master
+742a7893188658eaea4c183b85395472b3c90a50 a6b93ec58569d60b55136a7ff3f5f576916e303c Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510717 -0500	merge release/0.0.2: Merge made by the 'recursive' strategy.
+a6b93ec58569d60b55136a7ff3f5f576916e303c 805263aed3f51ee4f45aa2dfe70f8375c76900c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510734 -0500	checkout: moving from master to develop

data/.git/logs/refs/heads/develop

@@ -0,0 +1,4 @@
+0000000000000000000000000000000000000000 cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 Jonathan Barronville <jonathan@belairlabs.com> 1389508799 -0500	branch: Created from master
+cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508829 -0500	commit: First legit commit with all the code.
+ad48deb220c14f264ea31ae345163f53434a4a89 3053454fe8ce25790fb0bb99e085aed05f0920c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510245 -0500	merge hotfix/0.0.1-hotfix-small-update-001: Merge made by the 'recursive' strategy.
+3053454fe8ce25790fb0bb99e085aed05f0920c9 805263aed3f51ee4f45aa2dfe70f8375c76900c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510694 -0500	commit: You piss me off RubyGems.

data/.git/logs/refs/heads/master

@@ -0,0 +1,4 @@
+0000000000000000000000000000000000000000 cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 Jonathan Barronville <jonathan@belairlabs.com> 1389508799 -0500	commit (initial): Initial commit
+cb4945b0775afb714f0f6f1fe5fc53ad5daf8985 dfa83063026d1177200981794e135a1e8843e56a Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508846 -0500	merge release/0.0.1: Merge made by the 'recursive' strategy.
+dfa83063026d1177200981794e135a1e8843e56a 742a7893188658eaea4c183b85395472b3c90a50 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510236 -0500	merge hotfix/0.0.1-hotfix-small-update-001: Merge made by the 'recursive' strategy.
+742a7893188658eaea4c183b85395472b3c90a50 a6b93ec58569d60b55136a7ff3f5f576916e303c Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510717 -0500	merge release/0.0.2: Merge made by the 'recursive' strategy.

data/.git/logs/refs/remotes/origin/develop

@@ -0,0 +1,3 @@
+0000000000000000000000000000000000000000 ad48deb220c14f264ea31ae345163f53434a4a89 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508910 -0500	update by push
+ad48deb220c14f264ea31ae345163f53434a4a89 3053454fe8ce25790fb0bb99e085aed05f0920c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510255 -0500	update by push
+3053454fe8ce25790fb0bb99e085aed05f0920c9 805263aed3f51ee4f45aa2dfe70f8375c76900c9 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510745 -0500	update by push

data/.git/logs/refs/remotes/origin/master

@@ -0,0 +1,3 @@
+0000000000000000000000000000000000000000 dfa83063026d1177200981794e135a1e8843e56a Jonathan Barronville <jonathan.barronville@jebbit.com> 1389508910 -0500	update by push
+dfa83063026d1177200981794e135a1e8843e56a 742a7893188658eaea4c183b85395472b3c90a50 Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510255 -0500	update by push
+742a7893188658eaea4c183b85395472b3c90a50 a6b93ec58569d60b55136a7ff3f5f576916e303c Jonathan Barronville <jonathan.barronville@jebbit.com> 1389510745 -0500	update by push

data/.git/objects/00/385de4f2cdb2e486b6162bbe9ceded2c9de149

@@ -0,0 +1 @@
+x
}�;o1���SA��	�� �)(-��{�%����>���jF߬�4\�s�4��!�D�