summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDave Rolsky <autarch@urth.org>2011-02-15 18:25:38 -0600
committerÆvar Arnfjörð Bjarmason <avar@cpan.org>2011-02-16 00:33:25 +0000
commitc222ef4643569ab52b77652219561edee7a72409 (patch)
tree2d266230926e6a24f36987e8d06e874610e4e612
parent77b02b233b8508a437602a467d3bc847d684c6d2 (diff)
downloadperl-c222ef4643569ab52b77652219561edee7a72409.tar.gz
s/perlrepository/perlgit/g
Signed-off-by: Ævar Arnfjörð Bjarmason <avar@cpan.org>
-rw-r--r--Changes2
-rw-r--r--INSTALL2
-rw-r--r--Porting/release_managers_guide.pod2
-rw-r--r--README.cygwin2
-rw-r--r--pod/perlfaq.pod4
5 files changed, 6 insertions, 6 deletions
diff --git a/Changes b/Changes
index 08a0e43211..08bb959399 100644
--- a/Changes
+++ b/Changes
@@ -16,7 +16,7 @@ then run a command like
to view all the changes between 5.13.7 and 5.13.8.
-See pod/perlrepository.pod for more details on using git and accessing the
+See pod/perlgit.pod for more details on using git and accessing the
commit history.
In perl releases prior to 2009, the source tarball included a collection
diff --git a/INSTALL b/INSTALL
index 33faa6b54a..4bdf6d31b0 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1300,7 +1300,7 @@ various other operating systems.
If you plan to port Perl to a new architecture, study carefully the
section titled "Philosophical Issues in Patching and Porting Perl"
-in the file Porting/pumpkin.pod and the file pod/perlrepository.pod.
+in the file Porting/pumpkin.pod and the file pod/perlgit.pod.
Study also how other non-UNIX ports have solved problems.
=back
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 47e98e76cf..48e2e590b1 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -134,7 +134,7 @@ but ongoing. (No, a minicpan mirror is not sufficient)
You will need a working C<git> installation, checkout of the perl
git repository and perl commit bit. For information about working
-with perl and git, see F<pod/perlrepository.pod>.
+with perl and git, see F<pod/perlgit.pod>.
If you are not yet a perl committer, you won't be able to make a
release. Have a chat with whichever evil perl porter tried to talk
diff --git a/README.cygwin b/README.cygwin
index 986f91bcff..713c220679 100644
--- a/README.cygwin
+++ b/README.cygwin
@@ -563,7 +563,7 @@ be kept as clean as possible.
pod/perl561delta.pod pod/perl570delta.pod pod/perl572delta.pod
pod/perl573delta.pod pod/perl58delta.pod pod/perl581delta.pod
pod/perl590delta.pod pod/perlhist.pod pod/perlmodlib.pod
- pod/perltoc.pod pod.lst Porting/Glossary pod/perlrepository.pod
+ pod/perltoc.pod pod.lst Porting/Glossary pod/perlgit.pod
Porting/checkAUTHORS.pl
dist/Cwd/Changes ext/Compress-Raw-Zlib/Changes
ext/Compress-Raw-Zlib/README ext/Compress-Zlib/Changes
diff --git a/pod/perlfaq.pod b/pod/perlfaq.pod
index c00962fbd6..5e73ca59c1 100644
--- a/pod/perlfaq.pod
+++ b/pod/perlfaq.pod
@@ -24,7 +24,7 @@ at http://faq.perl.org/ . The perlfaq-workers periodically post extracts
of the latest perlfaq to comp.lang.perl.misc.
The perlfaq documents are in the perl source tree (see
-L<perlrepository>). The git repository notes all changes to the FAQ and
+L<perlgit>). The git repository notes all changes to the FAQ and
holds the latest version of the working documents and may vary
significantly from the version distributed with the latest version of
Perl. Check the repository before sending your corrections.
@@ -43,7 +43,7 @@ updates the answers. If you'd like to help review and update the
answers, check out comp.lang.perl.misc.
You can also fork the perl repository, make your changes, and send them
-to Perl 5 Porters. See L<perlrepository>.
+to Perl 5 Porters. See L<perlgit>.
=head2 What will happen if you mail your Perl programming problems to the authors?