similar to: plugin creation: where to put "include Reloadable"

In the actionpack-1.12.5\lib\action_controller\base.rb, you can see the definition: class Base include Reloadable::Subclasses ... And following is the definition of Reloadable: # Classes that include this module will automatically be reloaded # by the Rails dispatcher when Dependencies.mechanism = :load. module Reloadable class << self def included(base) #nodoc: raise

I can''t duplicate this problem on my local machine, but also can''t find any mentions of it on the Gmane archive, so thought I''d just throw in a quick mention in case anyone else comes across it. On Textdrive, using gem rails 1.1, in an app that works fine on my local machine, I get the following error in my production.log: "uninitialized constant

Hi Sebastion, I've attached the current configuration file from the server. I'm not sure how far you want to go down the "trying to get realize nice summary path" lines, but if svn_mailer somehow supported running an external script to process the commit and come up with the path that would be ideal for integration on the server. - Daniel On Fri, Jan 25, 2013 at 12:59 PM,

Is anybody working on this? If not, where might one start looking to fix this? -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of David Blaikie Sent: Monday, January 14, 2013 1:52 PM To: Sebastian Pop Cc: cfe-dev at cs.uiuc.edu Developers; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits

On Fri, Jan 25, 2013 at 2:06 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Sebastian Pop wrote: > > Hi Daniel, > > > > Daniel Dunbar wrote: > > > Hi Sebastion, > > > > > > I've attached the current configuration file from the server. > > > > > > I'm not sure how far you want to go down the "trying to get

Yup, I didn't either. I went ahead and hacked up a copy with that change and am switching it over now. - Daniel On Fri, Jan 25, 2013 at 3:06 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Daniel Dunbar wrote: > > I'm a bit hesitant to just hack up the installed copy of svnmailer, are > we > > sure this patch hasn't been dealt with in an upstream

Hi Everybody! As a newcomer to this list and to Rails per se I would like to to post my silly newbie questions ? be patient: 1. I''m not able to get rid of the welcome-aboard-screen. It says: > 3. Set up a default route and remove or rename this file > > Routes are setup in config/routes.rb. I''ve done the routing part ? at least I think I have! Now, as for the

Hi, Sebastian Pop wrote: > Chris Lattner wrote: > > I'm in favor of it. Of course, the truly awesomest thing would be something like: > > > > [cfe-commits] r167788 - [lib/Analysis] Fix bad CFG construction bug when handling C++ 'try' statements. > > commit_subject_template = %(prefix)s r%(revision)s - %(log)s I just realized that this line does not

Bump for something that would be good to do. On Fri, Nov 30, 2012 at 10:49 AM, Sebastian Pop <spop at codeaurora.org> wrote: > David Blaikie wrote: >> On Fri, Nov 30, 2012 at 9:43 AM, Sebastian Pop <spop at codeaurora.org> wrote: >> > Hi, >> > >> > Sebastian Pop wrote: >> >> Chris Lattner wrote: >> >> > I'm in favor of

On Fri, Nov 30, 2012 at 9:43 AM, Sebastian Pop <spop at codeaurora.org> wrote: > Hi, > > Sebastian Pop wrote: >> Chris Lattner wrote: >> > I'm in favor of it. Of course, the truly awesomest thing would be something like: >> > >> > [cfe-commits] r167788 - [lib/Analysis] Fix bad CFG construction bug when handling C++ 'try' statements.

Ok, this is done and seems to work. As far as Chris's request for getting "key directory" paths into the commit message, I thought about working on it, but in the end I'm not sure why we shouldn't just encourage people to self-tag their leading commit line with some sort of standard key ([MC], [Target/Mips], whatever). - Daniel On Fri, Jan 25, 2013 at 3:11 PM, Daniel

Jordan Rose wrote: > +John C and Daniel, who have access to the servers. > > Way back when this thread was first active I asked around off-list where this needs to happen, and Daniel and Tanya said this (respectively): > > >> I'd prefer to stick with using either svn-mailer or svnnotify, as those are the ones we use in other places. svnnotify in particular is very full

I''m working on the plugin for RBatis and a new little thing I''m toying around with called ActiveMessaging (sorry, David I stole the name from you from the TW AwayDay ;-)). Anyway, in both these applications I want to be able to have reloadable classes that don''t extend any of the standard built in ones. So, I don''t mean to offend the Eminent Core Members by

Daniel Dunbar wrote: > I'm a bit hesitant to just hack up the installed copy of svnmailer, are we > sure this patch hasn't been dealt with in an upstream version? I don't see that change in the last dev version: http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2 > > -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s > > %(from)s

David Blaikie wrote: > On Fri, Nov 30, 2012 at 9:43 AM, Sebastian Pop <spop at codeaurora.org> wrote: > > Hi, > > > > Sebastian Pop wrote: > >> Chris Lattner wrote: > >> > I'm in favor of it. Of course, the truly awesomest thing would be something like: > >> > > >> > [cfe-commits] r167788 - [lib/Analysis] Fix bad CFG

On 2008-11-04, at 08:12, Sebastian Redl wrote: > Mike Stump wrote: >> On Nov 3, 2008, at 1:39 PM, Sebastian Redl wrote: >>>> svn help cl >>>> >>>> [ runs away, much the same way someone that throws a lighted match >>>> into a pool of gasoline ] Probably wise. >>> "cl": unknown command. >> >> From svn 1.5:

Hi, Chris Lattner wrote: > > On Nov 15, 2012, at 2:28 PM, Chandler Carruth <chandlerc at google.com> wrote: > > >> [cfe-commits] r167788 - in /cfe/trunk: lib/Analysis/CFG.cpp test/Analysis/dead-stores.cpp > >> > >> with > >> > >> [cfe-commits] r167788 - Fix bad CFG construction bug when handling C++ 'try' statements. >

+John C and Daniel, who have access to the servers. Way back when this thread was first active I asked around off-list where this needs to happen, and Daniel and Tanya said this (respectively): >> I'd prefer to stick with using either svn-mailer or svnnotify, as those are the ones we use in other places. svnnotify in particular is very full featured, although we would need to install

Hi, I''m wondering if anyone has any recommendations as to where to put customizations of plugins. I''ve tried to put my current setting in environment.rb, so users of my plugin need to set a global constant before my plugin is loaded. But the next settings I will add are needed for a Rake task so I''m starting to believe that it would be better to have a separate

Sebastian Pop wrote: > Hi Daniel, > > Daniel Dunbar wrote: > > Hi Sebastion, > > > > I've attached the current configuration file from the server. > > > > I'm not sure how far you want to go down the "trying to get realize nice > > summary path" lines, but if svn_mailer somehow supported running an > > external script to