=================== BUG #4480: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4480&group_id=99

Changes by: Martin Brecher <[EMAIL PROTECTED]>
Date: Fri 07/25/2003 at 20:26 (GMT)

------------------ Additional Follow-up Comments ----------------------------
I will look into this when I submit the new/updated pages.
Currently I'm working on the gopen and openapp pages.



=================== BUG #4480: FULL BUG SNAPSHOT ===================


Submitted by: ehz                     Project: GNUstep                      
Submitted on: Fri 07/25/2003 at 19:51
Category:  None                       Severity:  5 - Major                  
Bug Group:  Bug                       Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  manpages have bad whatis entry

Original Submission:  lintian report:

Each manual page should start with a `NAME' section, which lists the name and a brief 
description of the page. These sections are parsed by `mandb' and stored in a database 
for the use of `apropos' and `whatis', so they must be in a certain format. This 
manual page apparently uses the wrong format and cannot be parsed by `mandb'.

  For information on how `NAME' sections should be written and a list of some common 
mistakes, please see the lexgrog(8) manual page.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Fri 07/25/2003 at 20:26       By: mb
I will look into this when I submit the new/updated pages.
Currently I'm working on the gopen and openapp pages.


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4480&group_id=99

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to