[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Who is responsible for SVN::Fs.3pm?

From: Eric S. Raymond <esr_at_thyrsus.com>
Date: 2005-01-21 08:59:23 CET

Ben Reser <ben@reser.org>:
> On Wed, Jan 19, 2005 at 12:26:25PM -0500, Eric S. Raymond wrote:
> > Who is responsible for the manual page SVN::Fs.3pm? It's part of the
> > subversion-perl RPM, but I can't find it in the repository.
>
> All perl module man pages are automatically generated from pods. Any
> complaints about the syntax should be directed to the authors of
> pod2man.
>
> The source file is subversion/bindings/swig/perl/native/Fs.pm

While I could complain voluminously about POD syntax, all I really
want is to stop this file from throwing an exception in doclifter(1).
For that purpose, adding enough POD markup to generate a trivial but
well-formed manual page will do (as it is, Subversion installs an
ill-formed empty man page).

If the right person would review and apply this trivial patch,
I would be grateful.

=============================================================================
--- Fs.pm (revision 11935)
+++ Fs.pm (working copy)
@@ -4,6 +4,20 @@
 package SVN::Fs;
 use SVN::Base qw(Fs svn_fs_);
 
+=head1 NAME
+
+SVN::Fs - Subversion filesystem functions
+
+=head1 DESCRIPTION
+
+SVN::Repos wraps the functions in svn_fs.h.
+
+=head2 METHODS
+
+Please consult the svn_fs.h section in the Subversion API.
+
+=cut
+
 package _p_svn_fs_t;
 
 our @methods = qw/youngest_rev revision_root revision_prop revision_proplist

=============================================================================

-- 
		Eric S. Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 21 09:03:02 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.