3 csets were pushed to core/stable: This trigger can both be called as a cus...

Changes were applied by marcel to core/stable level 10.
    The following csets were applied:
    
    ChangeSet
      1.2133 05/02/02 18:10:43 [email protected] +1 -0
      This trigger can both be called as a custom command, and as a trigger. The run location can therefore not be assumed.
      Test for it
    
      BitKeeper/triggers/pre-apply.qa
        1.43 05/02/02 18:10:41 [email protected] +8 -2
        This trigger can both be called as a custom command, and as a trigger. The run location can therefore not be assumed.
        Test for it
    
    ChangeSet
      1.2127.1.1 05/02/02 17:50:26 [email protected] +2 -0
      Doh! forgot a break. Amazing it didnt cause problems earlier. Maybe now it will start creating problems, cos this has been there for
      a long long time. PLEASE CHECK your CDATA usage.
      
      Sorry, I screwed up here.
      Anyway, this should fix bug #4026
    
      html/includes/xarBLCompiler.php
        1.268 05/02/02 17:50:24 [email protected] +1 -1
        Doh! forgot a break. Amazing it didnt cause problems earlier. Maybe now it will start creating problems, cos this has been there for
        a long long time. PLEASE CHECK your CDATA usage.
        
        Sorry, I screwed up here.
    
      docs/rfc/rfc0010.xml
        1.83 05/02/02 17:50:24 [email protected] +38 -1
        Somehow this didnt got pushed earlier. Documentation of the dtd attribute in the xar:blocklayout tag.
    
Links for the differences:
http://xaraya.com:15000/core/stable/[email protected]
http://xaraya.com:15000/core/stable/[email protected]