From 82abed73d3629453a5ffb6e253b78c192edbd808 Mon Sep 17 00:00:00 2001 From: William Metcalf Date: Wed, 29 Jul 2009 11:49:40 -0500 Subject: [PATCH] Moved GITGUIDE to doc/ --- GITGUIDE => doc/GITGUIDE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename GITGUIDE => doc/GITGUIDE (99%) diff --git a/GITGUIDE b/doc/GITGUIDE similarity index 99% rename from GITGUIDE rename to doc/GITGUIDE index 176032887e..41b4059a3c 100644 --- a/GITGUIDE +++ b/doc/GITGUIDE @@ -84,7 +84,7 @@ The following workflow is recommended by Evan and is the guideline for contribut git branch -d new_feature -When you're familiar with the workflow, you can use the rake tasks to help you out. For example, rake git will fetch the latest code from remote repo, rebase the current branch to master, fast-forward the changes to master and push the commits to the remote. This saves a lot of typing. Check rake -T git for all the git related tasks. +When you're familiar with the workflow, you can use the rake tasks to help you out. For example, rake git will fetch the latest code from remote repo, rebase the current branch to master, fast-forward the changes to master and push the commits to the remote. This saves a lot of typing. Check rake -T git for all the git related tasks. Taken from: http://rubinius.lighthouseapp.com/projects/5089/using-git