search for: michaelgalero

I just noticed I frequently encounter patches that need to be updated because of applied changes. Maybe this can be automated? Not automating the "updating of the patch" part, but the part where a comment is posted to the ticket so the submitter is informed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

So, given a sessionID, I have need to read and write the session stored information ''manually'', from _outside_ an actual Rails request/controller. Readers, I know your first response may be to tell me I don''t really want to do that. Trust me though, I really do, it makes sense for me in my case. I know this wouldn''t work if you''re using the new cookie

I''m referring to the vendor folder under activesupport/lib/ active_support folder. Are we supposed to be making changes to the files in this folder? I just submitted my first patch (a doc patch) to a file in this folder, and I just realized it could be an external project. Then I noticed the XML Builder project in RubyForge. I also just noticed that most of the files under the builder