summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod10
1 files changed, 5 insertions, 5 deletions
diff --git a/Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod b/Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod
index 6a754fb25ee..c226b071691 100644
--- a/Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod
+++ b/Master/tlpkg/tlperl/lib/CPANPLUS/Hacking.pod
@@ -2,7 +2,7 @@
=head1 NAME
-CPANPLUS::Hacking
+CPANPLUS::Hacking - developing CPANPLUS
=head1 DESCRIPTION
@@ -14,8 +14,8 @@ features or patches to CPANPLUS.
=head1 OBTAINING CPANPLUS
-Checkout CPANPLUS from its Subversion repository at
-L<http://oss.dwim.org/cpanplus-devel> .
+Checkout CPANPLUS from its GIT repository at
+L<https://github.com/jib/cpanplus-devel> .
=head1 INSTALLING CPANPLUS
@@ -73,7 +73,7 @@ better than not reporting it at all. Before you do so though, make
sure you have the B<latest> development snapshot, and the bug still
persists there. If so, report the bug to this address:
- cpanplus-devel@lists.sourceforge.net
+ bug-cpanplus@rt.cpan.org
A good C<patch> would have the following characteristics:
@@ -115,7 +115,7 @@ We prefer patches in the following format:
=item * Including patches for code + tests + docs
-=item * Sent per mail to cpanplus-devel@lists.sourceforge.net
+=item * Sent per mail to bug-cpanplus@rt.cpan.org
=item * With subject containing C<[PATCH]> + description of the patch