lib as patches

[j0hnsmith]

This is more a discussion than an issue and I'm not sure if it would be practical or not but here goes...

This repo appears to be (I haven't looked too closely at the actual code) a fork of angular resource. It seems to me that it would be far easier to pull changes from angular resource if this project was a series of patches to angular resource (1 patch per django specific feature to add/change), then the patches could be applied against each new version of angular resource as it's released.

Obviously the patches would have to be modified from time to time when they don't apply cleanly however we'd avoid the current situation where angular resource has moved forward (a bit of an assumption) but this fork hasn't. I suspect it might even make adding new features even easier.