gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] navidoc newpeg.py


From: Asko Soukka
Subject: [Gzz-commits] navidoc newpeg.py
Date: Fri, 25 Apr 2003 08:29:33 -0400

CVSROOT:        /cvsroot/navidoc
Module name:    navidoc
Changes by:     Asko Soukka <address@hidden>    03/04/25 08:29:33

Modified files:
        .              : newpeg.py 

Log message:
        twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/navidoc/navidoc/newpeg.py.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: navidoc/newpeg.py
diff -u navidoc/newpeg.py:1.1 navidoc/newpeg.py:1.2
--- navidoc/newpeg.py:1.1       Fri Apr 25 03:52:06 2003
+++ navidoc/newpeg.py   Fri Apr 25 08:29:33 2003
@@ -21,7 +21,7 @@
 # MA  02111-1307  USA
 # 
 
-#$Id: newpeg.py,v 1.1 2003/04/25 07:52:06 humppake Exp $
+#$Id: newpeg.py,v 1.2 2003/04/25 12:29:33 humppake Exp $
 
 #
 # Written by Asko Soukka
@@ -87,7 +87,7 @@
 
 Peg name: %s
 Peg directory: %s%s
-Author: %s(%s)
+Author: %s (%s)
 ****************************************
 """ % (peg_dir,
        slashify(peg_path),
@@ -107,7 +107,7 @@
 out = open(slashify(slashify(peg_path)+peg_dir+'--'+peg_author_nick) \
            +'peg.rst', 'w')
 localtime = time.localtime()
-date = '%s-%s-%s' % (localtime[0], localtime[1], localtime[2])
+date = '%s-%02d-%02d' % (localtime[0], localtime[1], localtime[2])
 out.write("""
 ==========================================================================
 PEG %s--%s:
@@ -115,8 +115,8 @@
 
 :Authors:  %s
 :Date-Created: %s
-:Last-Modified: $Date: 2003/04/25 07:52:06 $
-:Revision: $Revision: 1.1 $
+:Last-Modified: $Date: 2003/04/25 12:29:33 $
+:Revision: $Revision: 1.2 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -133,11 +133,11 @@
 Issues
 ======
 
-After this section, there should be an Issues section (following the
-example of OpenGL extension specs), which should contain the open
-questions related to this PEG. Once an issue is resolved, it is often
-good to leave the resolution and the rationale behind the resolution
-into the Issues section
+There should be an Issues section (following the example of OpenGL
+extension specs), which should contain the open questions related to
+this PEG. Once an issue is resolved, it is often good to leave the
+resolution and the rationale behind the resolution into the Issues
+section
 
 Changes
 =======
@@ -157,4 +157,7 @@
 out.write('*.gen.*'+"\n")
 out.close()
 
-print 'Creation of PEG template completed.'
+print """
+Creation of PEG template completed.
+%s
+""" % (slashify(peg_path)+peg_dir+'--'+peg_author_nick)




reply via email to

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