0001-It-should-be-using-rb_raise-not-signal-s-raise.patch

From 8d25e071518a2637fdfd3442ec10b5f71b2a7f61 Mon Sep 17 00:00:00 2001
From: Luis Lavena <luislavena@gmail.com>
Date: Tue, 14 Dec 2010 20:23:52 -0300
Subject: [PATCH 1/2] It should be using rb_raise, not signal's raise

---
 ext/rugged/rugged_repo.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/ext/rugged/rugged_repo.c b/ext/rugged/rugged_repo.c
index 667be0e..74626b5 100644
--- a/ext/rugged/rugged_repo.c
+++ b/ext/rugged/rugged_repo.c
@@ -177,10 +177,10 @@ static VALUE rb_git_repo_add_backend(VALUE self, VALUE rb_backend)
 	Data_Get_Struct(self, rugged_repository, repo);
 
 	if (!rb_obj_is_kind_of(rb_backend, rb_cRuggedBackend))
-		raise(rb_eTypeError, "expecting a subclass of Rugged::Backend");
+		rb_raise(rb_eTypeError, "expecting a subclass of Rugged::Backend");
 
 	if (rb_obj_is_instance_of(rb_backend, rb_cRuggedBackend))
-		raise(rb_eTypeError, "create a subclass of Rugged::Backend to define your custom backend");
+		rb_raise(rb_eTypeError, "create a subclass of Rugged::Backend to define your custom backend");
 
 	Data_Get_Struct(rb_backend, rugged_backend, backend);
 
-- 
1.7.3.1.msysgit.0