Bug 11856: Add confirm option to POD in advance_notices.pl

Also removes a commented line that changed the value of $confirm.
If it would default to 1, we do not need it at all.
I am not saying that we need it, but just documenting that we have it.

Signed-off-by: Marc Véron <veron@veron.ch>
Small change in documentation.

Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com>
Signed-off-by: Galen Charlton <gmc@esilibrary.com>

diff --git a/misc/cronjobs/advance_notices.pl b/misc/cronjobs/advance_notices.pl
index 405b0e1..c7c2e0f 100755 (executable)
--- a/misc/cronjobs/advance_notices.pl
+++ b/misc/cronjobs/advance_notices.pl
@@ -91,7 +91,10 @@ the patrons are printed to standard out.
 
 Defines the maximum number of days in advance to send advance notices.
 
+=item B<-c>
 
+Confirm flag: Add this option. The script will only print a usage
+statement otherwise.
 
 =item B<--itemscontent>
 
@@ -160,7 +163,6 @@ messages to patrons when their messages are overdue.
 
 # These are defaults for command line options.
 my $confirm;                                                        # -c: Confirm that the user has read and configured this script.
-# my $confirm     = 1;                                                # -c: Confirm that the user has read and configured this script.
 my $nomail;                                                         # -n: No mail. Will not send any emails.
 my $mindays     = 0;                                                # -m: Maximum number of days in advance to send notices
 my $maxdays     = 30;                                               # -e: the End of the time period