perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/2.0/api README
Date Mon, 27 Jan 2003 09:02:28 GMT
stas        2003/01/27 01:02:28

  Modified:    src/docs/2.0/api README
  Log:
  reality update
  
  Revision  Changes    Path
  1.2       +0 -17     modperl-docs/src/docs/2.0/api/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/README,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README	2 Oct 2001 15:26:29 -0000	1.1
  +++ README	27 Jan 2003 09:02:28 -0000	1.2
  @@ -3,26 +3,9 @@
   autogenerated it's much easier to keep the documentation in a separate
   place.
   
  -Each sub-project will have its own directory under docs/src/api
  -
  -Here is an example:
  -
  -docs/src/api:
  -  mod_perl-2.0/APR/Table.pod 
  -  mod_perl-2.0/Apache/RequestRec.pod 
  -  mod_perl-2.0/Apache/compat.pod
  -  Apache-Test/Apache/Test.pod
  -  Apache-Registry/Apache/Registry.pod
  -
   Keeping all the docs under the same directory makes it easy to
   distribute only the documentation, especially simplify the build,
   since they all live in a separate modperl-docs project.
  -
  -So modperl-2.0's API goes into docs/src/api/mod_perl-2.0,
  -Apache-Test's into docs/src/api/Apache-Test and etc.
  -
  -If later on we want to move directories around, this is very easy to
  -do without losing cvs history.
   
   That's said, when you send in new patches, from now on please don't
   forget to send documentation patches. It's much easier and nicer to
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message