Import cvs-mailcommit_1.19.orig.tar.gz

[dgit import orig cvs-mailcommit_1.19.orig.tar.gz]

2 files changed, 733 insertions, 0 deletions

diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..d60c31a
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/cvs-mailcommit b/cvs-mailcommit
new file mode 100755
index 0000000..dde1677
--- /dev/null
+++ b/cvs-mailcommit
@@ -0,0 +1,393 @@
+#! /usr/bin/perl
+
+# cvs-mailcommit - Send CVS commitments via mail
+# Copyright (c) 1998,2004  Martin Schulze <joey@infodrom.org>
+#
+# $Id: cvs-mailcommit,v 1.19 2004/08/09 15:48:09 joey Exp $
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
+
+# For testing, call this program like:
+#   echo "Logmsg" | CVSROOT=/cvs/webwml ./cvs-mailcommit -m $LOGNAME --from "$LOGNAME@`hostname -f`" --cvs 'CVSROOT loginfo,1.10,1.11' --diff
+
+# To extract the inline documentation, run the following command:
+#   pod2html cvs-mailcommit > cvs-mailcommit.1
+# To read this documentation, just type
+#   perldoc cvs-mailcommit
+
+use Getopt::Long;
+
+=head1 NAME
+
+cvs-mailcommit - Send CVS commitments via mail
+
+=head1 SYNOPSIS
+
+B<cvs-mailcommit> [options] [version*]
+
+=head1 DESCRIPTION
+
+B<cvs-mailcommit> is a helper application to CVS to help people keep
+track of CVS repositories via mail.  It is hooked into the CVS system
+via the B<CVSROOT>/I<loginfo> file.  It will read modification
+information from CVS via B<stdin> and require version information via
+the commandline.
+
+B<cvs-mailcommit> will send differences of modified files or entire
+new files via mail to the denoted address.
+
+You'll have to hook it into CVS for each module in a repository that
+you want to monitor via mail.  See B<INSTALLATION> below
+
+=cut
+
+$sendmail = "/usr/lib/sendmail";
+$rcsdiff = "rcsdiff";
+$co = "co";
+
+$opt_xloop = '';
+$opt_cvs = '';
+$opt_from = '';
+$opt_replyto = '';
+$opt_approved = '';
+$opt_diff = 0;
+$opt_full = 0;
+$opt_maxlines = 400;
+@opt_mailto = ();
+$opt_cvsroot = '';
+$opt_dir = '';
+
+# A way to alter the default settings
+$cfg = "/etc/cvs-mailcommit.pl";
+require $cfg if (-r $cfg);
+
+my %options = (
+               'mailto|m=s' => \@opt_mailto,
+               'diff|d' => \$opt_diff,
+               'full' => \$opt_full,
+               'xloop=s' => \$opt_xloop,
+               'from=s' => \$opt_from,
+               'replyto=s' => \$opt_replyto,
+               'approved=s' => \$opt_approved,
+               'maxlines=i' => \$opt_maxlines,
+               'cvs=s' => \$opt_cvs,
+               'root=s' => \$opt_cvsroot,
+               'dir=s' => \$opt_dir,
+              );
+
+# Filter out new directory creations
+# Arguments: '- New directory' NONE NONE
+#
+$pivot = 0;
+while ($pivot <= $#ARGV) {
+    splice (@ARGV, $pivot, $pivot+2) if ($ARGV[$pivot] eq '- New directory');
+    $pivot++;
+}
+
+GetOptions (%options);
+
+=head1 OPTIONS
+
+This program supports the following arguments.  When the arguments
+don't make sense the program won't do anything.
+
+=over 6
+
+=item B<-m> I<address>, B<--mailto> I<address>
+
+Send the mail to the specified I<address>.  This option can be
+specified on the commandline multiple times.
+
+=item B<--diff>
+
+Generate unified diffs for all modified files.
+
+=item B<--full>
+
+Include the entire fill for newly created files that were added to the
+repository.
+
+=item B<--maxlines> I<nnn>
+
+You can specify how many lines per file may be quoted in the resulting
+mail.  Limiting the number of quoted lines may be useful for
+repositories with excessive changes that are similar.  The default is
+to copy 400 lines.
+
+=item B<--xloop> I<address>
+
+Include a special B<X-Loop> header in the generated mail.  This is
+intended for users to be able to filter CVS mails by a common header
+line.  The line will look like
+
+X-Loop: I<address>
+
+=item B<--from> I<address>
+
+Generate a B<From:>-line of the form
+
+From: CVS User foo <I<address>>
+
+Otherwise the local user the program runs under will be used instead
+of I<address>.  With this parameter you can ensure that all such mails
+will be sent with the same from line, which may be useful for
+moderated lists or some where only subscribers may write.
+
+=item B<--replyto> I<address>
+
+Try to redirect replies to CVS mails to another address by setting
+proper header lines such as
+
+Reply-To: I<address>
+
+Mail-Followup-To: I<address>
+
+=item B<--approved> I<address>
+
+Include a special B<Approved:>-line in the mail.  This header is
+intended for moderated mailing-lists to pass the SmartList moderation
+mechanism.  The created header will look like
+
+Approved: I<address>
+
+=item B<--cvs> I<version string>
+
+This option carries the CVS version info from CVS into the program.
+It will be added automatically by CVS.  When installing this program
+into the B<loginfo> file of a CVS repository, you will need to add the
+following option:
+
+B<--cvs> %{sVv}
+
+If you want to test this program manually you'll have to supply the
+module directory and the modified files including the old and new
+versions.  This will look like
+
+--cvs 'CVSROOT loginfo,1.1,1.2'
+
+This option is only usful for old-style CVS format strings (i.e. prior
+to CVS 1.12.6).  You can continue using old-style format strings with
+newer cvs if you write %1{sVv} and set B<UseNewInfoFmtStrings>=I<yes>
+in CVSROOT/config.  For more recent versions of CVS you should,
+however, use the new --root and --dir arguments and place %{sVv} at
+the end of the commandline.
+
+=item B<--root> I<cvs repository>
+
+Specify the CVS repository directory.  This is normally done by the
+CVS server.  Prior to version 1.12 the repository was transmitted to
+the log processor via the B<CVSROOT> environment variable.  The
+parameter to this option is normally filled in by CVS using the %r
+format string:
+
+B<--root> %r
+
+=item B<--dir> I<module directory>
+
+Specify the directory within the CVS repository in which directories
+or file were added or modified.  The parameter to this option is
+normally filled in by CVS using the %p format string:
+
+B<--dir> %p
+
+=back
+
+=cut
+
+exit 0 if (!@opt_mailto);
+
+# $opt_cvs looks like
+#   foo/waz bar,1.4,1.5 foo,1.2,1.3
+# or
+#   foo gnatz,1.3,1.4
+#
+if ($opt_cvs) {
+    @cvs_arr = split (/ /,$opt_cvs);
+    $opt_dir = $cvs_arr[0];
+    $module_dir = $ENV{'CVSROOT'} . "/" . shift(@cvs_arr);
+} else {
+    if ($opt_cvsroot) {
+	if ($opt_dir) {
+	    $module_dir = $opt_cvsroot ."/". $opt_dir;
+	} else {
+	    $module_dir = $opt_cvsroot;
+	}
+	while ($#ARGV >= 2) {
+	    push (@cvs_arr, shift (@ARGV) .",". shift (@ARGV) .",". shift (@ARGV));
+	}
+	while ($#ARGV > -1) {
+	    printf "Unknown argument '%s', deleting.\n", shift (@ARGV);
+	}	
+    } else {
+	print STDERR "No --cvs and no --root (and --dir) specified, aborting.\n";
+    }
+}
+
+$login = $ENV{'CVS_USER'} || $ENV{'LOGNAME'}|| getlogin || (getpwuid($<))[0] || "nobody";
+$logname = $ENV{'LOGNAME'}|| getlogin || (getpwuid($<))[0] || $ENV{'CVS_USER'} || "nobody";
+
+if (open (M, "|$sendmail -t")) {
+# if (open (M, ">-")) {
+    printf M "To: %s\n", join(",",@opt_mailto);
+    printf M "Subject: CVS %s\n", $opt_dir;
+    if ($opt_from) {
+	printf M "From: \"CVS User %s\" <%s>\n", $login, $opt_from;
+    } else {
+	printf M "From: \"CVS User %s\" <%s>\n", $login, $logname;
+    }
+    if ($opt_replyto) {
+	printf M "Reply-To: %s\n", $opt_replyto;
+	printf M "Mail-Followup-To: %s\n", $opt_replyto;
+    }
+    printf M "Approved: %s\n", $opt_approved if ($opt_approved);
+    printf M "X-Loop: %s\n", $opt_xloop if ($opt_xloop);
+    print  M "\n";
+    print M while (<>);
+
+    if ($opt_diff) {
+	print  M "\n";
+	foreach $cstr (@cvs_arr) {
+	    ($file,$oldver,$newver) = split (/,/,$cstr);
+	    next if ($oldver eq "" || $newver eq "");
+	    if ($oldver ne "NONE") {
+		# print "$rcsdiff -r$oldver -r$newver -u $module_dir/$file|\n";
+		if (open (R, "$rcsdiff -r$oldver -r$newver -u $module_dir/$file 2>/dev/null |")) {
+		    $lines = 0;
+		    while (<R>) {
+			$lines++;
+			print M if ($lines <= $opt_maxlines);
+		    }
+		    close (R);
+		    printf M "\n[%d lines skipped]\n", $lines - $opt_maxlines if ($lines > $opt_maxlines);
+		}
+	    }
+	}
+    }
+
+    # Process new files
+    if ($opt_full) {
+	print  M "\n";
+	foreach $cstr (@cvs_arr) {
+	    ($file,$oldver,$newver) = split (/,/,$cstr);
+	    next if ($oldver ne "NONE" || $newver ne "1.1");
+
+	    my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst)
+		= gmtime(time);
+
+	    my $date = sprintf ("%4d/%02d/%02d %02d:%02d:%02d",
+				$year+1900, $mon+1, $mday, $hour,$min,$sec);
+
+	    if (open (R, "$co -p -r$newver $module_dir/$file 2>/dev/null |")) {
+		printf M "--- %s/%s\t%s\tNONE\n", $module_dir, $file, $date;
+		printf M "+++ %s/%s\t%s\t%s\n", $module_dir, $file, $date, $newver;
+		while (<R>) {
+		    $lines++;
+		    print M if ($lines <= $opt_maxlines);
+		}
+		close (R);
+		printf M "\n[%d lines skipped]\n", $lines - $opt_maxlines if ($lines > $opt_maxlines);
+	    } else {
+		print M "Cannot open $co, huh, $!\n";
+	    }
+	}
+    }
+
+    close (M);
+}
+
+=head1 CONFIGURATION FILE
+
+B<cvs-mailcommit> supports an additional configuration file
+I</etc/cvs-mailcommit.pl> so that hard-coded default values can be
+overwritten.  The file is included via require and hence needs to
+contain valid Perl code, which evaluates to I<true>.  I.e. place B<1;>
+at the end of the file.
+
+=head1 INSTALLATION
+
+The B<CVSROOT>/I<loginfo> file controls where B<cvs commit> log
+information is sent.  The first entry on a line is a regular
+expression which must match the directory (alias module) that the
+change is being made to, relative to the $B<CVSROOT>.  If a match is
+found, then the remainder of the line is a filter program that should
+expect log information on its standard input.
+
+A I<loginfo> line looks like
+
+<directory>    <command> --<option> --<option>
+
+=head1 NOTES
+
+The B<--cvs> option is only valid for old-style CVS format strings
+prior to version 1.12.6 of CVS with I<%{sVv}> or for new-style CVS
+format strings using the compatibility hack with I<%1{sVv}>.
+
+For new-style CVS format strings for CVS version 1.12.6 or higher
+B<--cvs> must not be used anymore, but instead B<--root> and B<--dir>
+are required.  The version information I<%{sVv}> must be added at the
+end of the command line.
+
+=head1 EXAMPLE
+
+Assume you want to monitor changes in the B<CVSROOT> module, then you
+may want to use the following line.
+
+    CVSROOT	cvs-mailcommit \
+      --mailto master@host.org \
+      --from cvs@cvshost.com \
+      --cvs %{sVv} --diff --full
+
+If you want to distribute changes in a module via a mailing list where
+only these log messages should appear you may have to add an X-Loop:
+or Approved: header line.
+
+    webwml	cvs-mailcommit \
+      --mailto master@host.org \
+      --from cvs@cvshost.com \
+      --approved cvsmaster@cvshost.com \
+      --cvs %{sVv} --diff --full
+
+The above configuration lines are valid only for old-style format
+strings.  With a more recent version of CVS (1.12.6 or newer) you'll
+have to replace I<%{sVv}> with I<%1{sVv}> and set
+B<UseNewInfoFmtStrings> to I<yes> in I<CVSROOT/config>.
+
+For new-style CVS format strings other parameters need to be used
+since CVS changed the syntax and semantics.  You must not use the
+B<--cvs> option anymore but need to use B<--root> and B<--dir> and
+place the version list at the end.  The last example converted for
+new-style format strings looks like the following:
+
+    webwml	cvs-mailcommit \
+      --mailto master@host.org \
+      --from cvs@cvshost.com \
+      --approved cvsmaster@cvshost.com \
+      --diff --full --root %r --dir %p %{sVv}
+
+To improve readability, the above lines were broken up into several
+lines using normal continuation lines.  This is not supported by CVS.
+You will have to write it in one single line.
+
+=head1 WARNING
+
+CVS does not support continuation lines (multiple lines per command)
+in the B<CVSROOT>/I<loginfo> file.  You'll have to write each filter
+in a single line of its own.
+
+=head1 SOURCE
+
+http://www.infodrom.org/Infodrom/tools/cvs-mailcommit.html
+
+=cut