Kevin A. McGrail writes: > Taking some off-list discussion back on list... > > > The podchecker reports some > > > > unresolved internal link 'TAGGING' > > > > warnings, don't know what - if anything - can be done about it: > Interesting. OK, I only get two errors with 5.10.1 but now have a system > generating the same errors. > > TAGGING is a missing link. There is no section marked TAGGING. > > Spot checking, that pod information is in spamassassin.raw > > spamassassin/"TAGGING" > > The deprecated section WARNING means to remove (1) > > This patch fixes both those warnings. Look good to you? > > Index: lib/spamassassin-run.pod > =================================================================== > --- lib/spamassassin-run.pod (revision 1104416) > +++ lib/spamassassin-run.pod (working copy) > @@ -74,7 +74,7 @@ > spam for later filtering using the user's own mail user-agent > application. > > -The default tagging operations that take place are detailed in > L</TAGGING>. +The default tagging operations that take place are detailed > in > L<spamassassin/"TAGGING">. > > By default, message(s) are read in from STDIN (< I<mailmessage>), or > from specified files and directories (I<path> ...) STDIN and files > Index: masses/perceptron.pod > =================================================================== > --- masses/perceptron.pod (revision 1104416) > +++ masses/perceptron.pod (working copy) > @@ -25,6 +25,6 @@ > > =head1 SEE ALSO > > -L<logs-to-c(1)> > +L<logs-to-c> > > =cut
> This patch fixes both those warnings. Look good to you? Looks good to me, thanks. Please apply. Mark
