summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorJerry D. Hedden <jdhedden@cpan.org>2007-04-16 06:44:36 -0400
committerH.Merijn Brand <h.m.brand@xs4all.nl>2007-04-16 15:01:31 +0000
commit2c8694a778a4cb9e4248cb373d54ec96f4d26baa (patch)
treef6bab51ed2e0857731867b87430fd34b8032b521 /pod
parent40c8724780d55d498f28a1a86b94645ad6ad2fef (diff)
downloadperl-2c8694a778a4cb9e4248cb373d54ec96f4d26baa.tar.gz
Re: [PATCH] Mention sorting MANIFEST in perlhack.pod
From: "Jerry D. Hedden" <jdhedden@cpan.org> Message-ID: <1ff86f510704160744j9ae934cv9fef077afe3ca516@mail.gmail.com> p4raw-id: //depot/perl@30968
Diffstat (limited to 'pod')
-rw-r--r--pod/perlhack.pod6
1 files changed, 4 insertions, 2 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 21968d76f7..3d0878e194 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -602,8 +602,10 @@ the 5.8 pumpking decides which of those patches is to be backported to the
maint branch. Only patches that survive the heat of the development
branch get applied to maintenance versions.
-Your patch should also update the documentation and test suite. See
-L<Writing a test>.
+Your patch should update the documentation and test suite. See
+L<Writing a test>. If you have added or removed files in the distribution,
+edit the MANIFEST file accordingly, sort the MANIFEST file using
+C<make manisort>, and include those changes as part of your patch.
Patching documentation also follows the same order: if accepted, a patch
is first applied to B<development>, and if relevant then it's backported