[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Groff-commit] groff MANIFEST

From: Werner LEMBERG
Subject: [Groff-commit] groff MANIFEST
Date: Tue, 29 Jan 2013 08:08:33 +0000

CVSROOT:        /cvsroot/groff
Module name:    groff
Changes by:     Werner LEMBERG <wl>     13/01/29 08:08:33

Modified files:
        .              : MANIFEST 

Log message:


RCS file: /cvsroot/groff/groff/MANIFEST,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- MANIFEST    24 Jan 2013 12:27:39 -0000      1.18
+++ MANIFEST    29 Jan 2013 08:08:33 -0000      1.19
@@ -1,4 +1,4 @@
-    Copyright 2001-2006, 2009-2011
+    Copyright 2001-2006, 2009-2013
       Free Software Foundation, Inc.
     Copying and distribution of this file, with or without modification,
@@ -145,22 +145,18 @@
 - Documentation in other formats are located in the `doc' directory,
   including the groff info file, tutorials, and manuals.
-Man-pages have source files ending in `.man'.  When running `make'
-they are transformed into an ending `.n'.  So it is very hard to
-decide into which section the man-page shall go.  Here is a shell
-command that finds all man-pages and writes the section number after
-each file name:
-find -type f |
-grep '[.]man$' |
-sort |
-xargs grep -e '^[.]TH ' |
-sed -e '
-s/^\(.\+\): address@hidden(.*\)address@hidden/\1 \2/
-This shell command shall only be run when your in the top directory of
-the groff source tree (this file should be there named MANIFEST).
+Man-pages have source files ending in `.man'.  Running `make' processes
+the files and uses `.n' as the new file extension.  In both cases it is
+difficult to quickly decide into which section the man-page shall go. 
+Here is a shell command (to be called from the top directory of the
+groff source tree) that finds all man-pages and writes the section
+number after each file name:
+  find -type f \
+  | grep '[.]man$' \
+  | sort \
+  | xargs grep -e '^[.]TH ' \
+  | sed -e 's/^\(.\+\): address@hidden(.*\)address@hidden/\1 \2/'
 4) The roff parser

reply via email to

[Prev in Thread] Current Thread [Next in Thread]