--- a/bin/rpi	Mon Sep 05 12:33:46 2011 +0200
+++ b/bin/rpi	Mon Sep 19 11:56:13 2011 +0200
@@ -8,30 +8,6 @@
 use Mail::Sendmail;
 use Sys::Hostname::Long;
 
-=head1 Name
-
-rpi - a wrapper around B<reprepro processincoming>
-
-=head1 Description
-
-Until B<reprepro> supports a better mechanism for sending notifications for
-rejected packages we just execute B<reprepro processincoming> and parse its
-stdout and its stderr. Everything matching C<$important> patterns will be sent
-to either the signer of the changes file, the changer (from the B<Changed-By>
-field if present) or the maintainer (from the B<Maintainer> field). Depending
-on the type of message suggestions for problem resolution may be added. To
-enable us to determine which message relates to which .changes file we need a
-patched B<reprepro>: L<https://keller.schlittermann.de/hg/ius/diffs/raw-file/8d32753c0599/reprepro/3.5.2/changes-file-process-messages.patch>.
-
-To avoid possibly bothering random people we can limit possible recipients with
-a regular expression in C<$valid_receivers>. Any output matching the
-C<$unimportant> regular expression will not be sent to anyone. If we cant
-determine anyone to send the notification to we will try to send it to the
-C<$fallback> address. Anything matching none of the defined patterns will be
-sent to the C<$fallback> address too. Everything will be printed to stdout.
-
-=cut
-
 my $hostname = hostname_long;
 for (*STDERR, *STDOUT) { select $_; $|=1; }
 
@@ -384,3 +360,29 @@
 sub END {
   print "[$0]: Finished at ", scalar localtime, "\n";
 }
+
+__END__
+
+=head1 Name
+
+rpi - a wrapper around B<reprepro processincoming>
+
+=head1 Description
+
+Until B<reprepro> supports a better mechanism for sending notifications for
+rejected packages we just execute B<reprepro processincoming> and parse its
+stdout and its stderr. Everything matching C<$important> patterns will be sent
+to either the signer of the changes file, the changer (from the B<Changed-By>
+field if present) or the maintainer (from the B<Maintainer> field). Depending
+on the type of message suggestions for problem resolution may be added. To
+enable us to determine which message relates to which .changes file we need a
+patched B<reprepro>: L<https://keller.schlittermann.de/hg/ius/diffs/raw-file/8d32753c0599/reprepro/3.5.2/changes-file-process-messages.patch>.
+
+To avoid possibly bothering random people we can limit possible recipients with
+a regular expression in C<$valid_receivers>. Any output matching the
+C<$unimportant> regular expression will not be sent to anyone. If we cant
+determine anyone to send the notification to we will try to send it to the
+C<$fallback> address. Anything matching none of the defined patterns will be
+sent to the C<$fallback> address too. Everything will be printed to stdout.
+
+=cut