There should be a rake -all option or something perhaps. If these "hidden" tasks aren't documented anywhere that a newbie can easily find them, then removing them doesn't seem like a good idea.
On Fri, Mar 4, 2011 at 11:26 PM, Jason King <[email protected]> wrote: > db:migrate:* are also missing, ie. down, redo, and up > > On Mar 4, 2011 9:40 AM, "Rodrigo Rosenfeld Rosas" <[email protected]> > wrote: >> On 4 mar, 14:34, Rodrigo Rosenfeld Rosas <[email protected]> wrote: >>> ... >>> >>> Note that several tasks have their descriptions commented out for some >>> reason. Is there any reasons to hide db:reset? >> >> Answering my own question, after git blame and git log 98381563: >> >> "Cut down even further on rake -T noise" >> >> It seems David thinks the db:reset task is a noise... >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-core?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
