summaryrefslogtreecommitdiff
path: root/pod/perlgit.pod
diff options
context:
space:
mode:
authorSteve Hay <steve.m.hay@googlemail.com>2012-09-13 22:16:44 +0100
committerSteve Hay <steve.m.hay@googlemail.com>2012-09-13 22:16:44 +0100
commit99cd8e461ab8bc340aed8e4c109bb32457f85bd0 (patch)
tree0c4d9aa30f935897b857c21b9d62c3f9daf08acd /pod/perlgit.pod
parent8700fd387632099e570555f059e008cb2dff2759 (diff)
downloadperl-99cd8e461ab8bc340aed8e4c109bb32457f85bd0.tar.gz
Fix a couple of headings in perlgit.pod which look to be the wrong level
Diffstat (limited to 'pod/perlgit.pod')
-rw-r--r--pod/perlgit.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perlgit.pod b/pod/perlgit.pod
index 1d2df2ed5e..6046d46351 100644
--- a/pod/perlgit.pod
+++ b/pod/perlgit.pod
@@ -481,7 +481,7 @@ the "first commit where the bug is solved".
C<git help bisect> has much more information on how you can tweak your
binary searches.
-=head1 Topic branches and rewriting history
+=head2 Topic branches and rewriting history
Individual committers should create topic branches under
B<yourname>/B<some_descriptive_name>. Other committers should check
@@ -606,7 +606,7 @@ to push your changes back with the C<camel> remote:
The C<fetch> command just updates the C<camel> refs, as the objects
themselves should have been fetched when pulling from C<origin>.
-=head1 Accepting a patch
+=head2 Accepting a patch
If you have received a patch file generated using the above section,
you should try out the patch.
@@ -708,7 +708,7 @@ because it runs a subset of tests under miniperl rather than perl.
=back
-=head3 On merging and rebasing
+=head2 On merging and rebasing
Simple, one-off commits pushed to the 'blead' branch should be simple
commits that apply cleanly. In other words, you should make sure your