| Commit History - (may be incomplete: see SVNWeb link above for full details) |
| Date | By | Description |
04 Aug 2012 04:06:10
1.2.1
|
swills  |
- Update to 1.2.1 |
02 Nov 2011 18:05:08
1.2.0
|
pgollucci  |
- Fix depend versions according to rubygems.org [again]
With Hat: ruby@
Tested by: P6 TB Full rubygem run |
27 Oct 2011 02:41:37
1.2.0
|
swills  |
- Update ruby-dm ports to latest versions |
16 Oct 2011 13:09:59
1.1.0
|
zi  |
- Update MAINTAINER to ruby@ for my ruby ports |
15 Jul 2011 21:15:29
1.1.0
|
zi  |
Update my email address on the ports I maintain.
Approved by: wxs@ (mentor) |
23 Jun 2011 19:43:15
1.1.0
|
pgollucci  |
- Fix up depencies versions after all the churn today |
23 Jun 2011 17:51:43
1.1.0
|
pgollucci  |
- Cannoicalize the WWW: [again],
- Save redirects s/http/https/ for github |
23 Jun 2011 17:45:18
1.1.0
|
pgollucci  |
- Update Data Mapper to 1.1.0
and its required dependecies
With Hat: ruby@
Sponsored by: RideCharge Inc. / TaxiMagic |
18 Jun 2011 18:46:40
1.0.4
|
swills  |
This gem provides the railtie that allows datamapper to hook
into rails3 and thus behave like a rails framework component.
Just like activerecord does in rails, dm-rails uses the railtie
API to hook into rails. The two are actually hooked into rails
almost identically.
Creating new datamapper apps on rails3 from scratch is actually
really easy. The following will guide you through the process.
WWW: http://rubygems.org/gems/dm-rails
PR: ports/157994
Submitted by: Ryan Steinmetz <rpsfa at rit.edu> |