From 6f56ac39f60976727952f47f417ee5d00a7b359d Mon Sep 17 00:00:00 2001
From: David Golden <dagolden@cpan.org>
Date: Tue, 13 Jul 2010 22:07:35 -0400
Subject: [PATCH] Revise perldelta template to group doc/utility bullets

---
 Porting/perldelta_template.pod | 25 ++++++++++++-------------
 1 file changed, 12 insertions(+), 13 deletions(-)

diff --git a/Porting/perldelta_template.pod b/Porting/perldelta_template.pod
index 56f2f50..4a1a4f6 100644
--- a/Porting/perldelta_template.pod
+++ b/Porting/perldelta_template.pod
@@ -115,19 +115,13 @@ XXX
 XXX Changes to files in F<pod/> go here.  Consider grouping entries by
 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
 
-[ Within each section, list entries as a =item entry ]
-
 =head2 New Documentation
 
 XXX Changes which create B<new> files in F<pod/> go here.
 
-=over 4
-
-=item L<XXX>
-
-XXX
+=head3 L<XXX>
 
-=back
+XXX Description of the purpose of the new file here
 
 =head2 Changes to Existing Documentation
 
@@ -135,11 +129,13 @@ XXX Changes which significantly change existing files in F<pod/> go here.
 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
 section.
 
+=head3 L<XXX>
+
 =over 4
 
-=item L<XXX>
+=item *
 
-XXX
+XXX Description of the change here
 
 =back
 
@@ -183,12 +179,15 @@ XXX
 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
 here. Most of these are built within the directories F<utils> and F<x2p>.
 
-[ List utility changes as a =item entry.  Use L<XXX> with program names to get
-proper documentation linking. ]
+[ List utility changes as a =head3 entry for each utility and =item
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
+
+=head3 L<XXX>
 
 =over 4
 
-=item L<XXX>
+=item *
 
 XXX
 
-- 
2.7.4