From 6b6443ab845c104e1fa9f4139169ef698c3831c7 Mon Sep 17 00:00:00 2001
From: Tom Ward <tom@popdog.net>
Date: Wed, 31 Aug 2011 19:12:46 +0100
Subject: [PATCH] When developing a gem, Gemfile.lock should not be checked
 into version control.

For the full rationale, see @wycats excellent article: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
---
 .gitignore   |  1 +
 Gemfile.lock | 31 -------------------------------
 2 files changed, 1 insertion(+), 31 deletions(-)
 delete mode 100644 Gemfile.lock

diff --git a/.gitignore b/.gitignore
index 1b10c47..2b18cd6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@ pkg/*
 *.rbc
 *.swp
 .bundle
+Gemfile.lock
diff --git a/Gemfile.lock b/Gemfile.lock
deleted file mode 100644
index 0e17ad7..0000000
--- a/Gemfile.lock
+++ /dev/null
@@ -1,31 +0,0 @@
-PATH
-  remote: .
-  specs:
-    guard-rails-assets (0.0.5)
-      guard
-      rake
-
-GEM
-  remote: http://rubygems.org/
-  specs:
-    diff-lcs (1.1.2)
-    guard (0.5.1)
-      thor (~> 0.14.6)
-    rake (0.9.2)
-    rspec (2.6.0)
-      rspec-core (~> 2.6.0)
-      rspec-expectations (~> 2.6.0)
-      rspec-mocks (~> 2.6.0)
-    rspec-core (2.6.4)
-    rspec-expectations (2.6.0)
-      diff-lcs (~> 1.1.2)
-    rspec-mocks (2.6.0)
-    thor (0.14.6)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  guard-rails-assets!
-  rake
-  rspec