…fault" This reverts commit 234a4ca. Reason: No big deal Ryan, only there's a very strict policy in docrails which allows public write access on the other hand. CHANGELOGs can only be edited in master. If this is added I'll make sure you get the credit for the patch.
…ternal railties rake tasks description.
…ization.textile file [#5779 state:resolved]
…tabases rake tasks.
… / none)
[#5539 state:committed] Commit 5714438 removed the hard-coded dependency on the memcache-client gem, and added this warning advising people to install it if needed. The problem is, however, that if people follow the advice literally and install the 'memcache' gem, they will wind up with a completely different thing, which is not API compatible with the memcache-client gem and which Rails can't work with. So, be explicit and tell users to install the 'memcache-client' gem. Signed-off-by: Santiago Pastorino <email@example.com>
… on rendering.
…SS template handler.
This commit moves all the template rendering logic that was hanging around AV::Base to renderer objects.
…is set [#3572 state:resolved] Signed-off-by: Xavier Noria <firstname.lastname@example.org>
Before this patch, every request in development caused the template to be compiled, regardless if it was updated in the filesystem or not. This patch now checks the timestamp and only compiles it again if any change was done. While this probably won't show any difference for current setups, but it will be useful for asset template handlers (like SASS), as compiling their templates is slower than ERb, Haml, etc.
…ons and fix it to work with new copying strategy
The purpose of this change is to allow copying fail on the same names. Migrations change database and they should be treated with caution, if 2 migrations are named the same it's much better to skip migration and allow user decide if it should be copied or not.