diff --git a/mozilla/webtools/bugzilla/.bzrrev b/mozilla/webtools/bugzilla/.bzrrev index c3951f06985..148e54cf4d6 100644 --- a/mozilla/webtools/bugzilla/.bzrrev +++ b/mozilla/webtools/bugzilla/.bzrrev @@ -1 +1 @@ -7052 \ No newline at end of file +7053 \ No newline at end of file diff --git a/mozilla/webtools/bugzilla/Bugzilla/Extension.pm b/mozilla/webtools/bugzilla/Bugzilla/Extension.pm index 2bd26c3ed7b..17b889b984a 100644 --- a/mozilla/webtools/bugzilla/Bugzilla/Extension.pm +++ b/mozilla/webtools/bugzilla/Bugzilla/Extension.pm @@ -381,7 +381,7 @@ described in the L section above. During your subroutine, you may want to know what values were passed as CGI arguments to the current script, or what arguments were passed to the current WebService method. You can get that data via -. +L. =head3 Adding New Hooks To Bugzilla @@ -447,8 +447,8 @@ named C: Note that it is I a subclass of C, because at the time that module requirements are being checked in L, C cannot be loaded. Also, just like F, -it ends with C<< __PACKAGE__->NAME; >>. Note also that it has the exact -same C name as F. +it ends with C<< __PACKAGE__->NAME; >>. Note also that it has the +B C name as F. This file may not use any Perl modules other than L, L, L, and @@ -483,8 +483,8 @@ which should have C as its package name. This allows any place in Bugzilla to load your modules, which is important -for some hooks. It even allows other extensions to load your modules. It -even allows you to install your modules into the global Perl install +for some hooks. It even allows other extensions to load your modules, and +allows you to install your modules into the global Perl install as F, if you'd like, which helps allow CPAN distribution of Bugzilla extensions. @@ -594,7 +594,7 @@ C
. This is the name of the hook--what you saw in C inside of the template you want to hook. In our example, this is -C. +C. =item