r66009 - /website/git.pod

[dmn at users.alioth.debian.org]

Author: dmn
Date: Sun Dec 19 18:59:11 2010
New Revision: 66009

URL: http://svn.debian.org/wsvn/?sc=1&rev=66009
Log:
frop bullets andd numbers from headings

Modified:
    website/git.pod

Modified: website/git.pod
URL: http://svn.debian.org/wsvn/website/git.pod?rev=66009&op=diff
==============================================================================
--- website/git.pod (original)
+++ website/git.pod Sun Dec 19 18:59:11 2010
@@ -19,14 +19,14 @@
 you'd need to ping them or stick with Subversion. Help is wanted for Git
 support in PET.
 
-=head1 1. The Tools
+=head1 The Tools
 
 Most of the tools you will be using will come from either the
 B<git-buildpackage> or the B<git> packages.
 
-=head1 2. Packaging walkthrough
-
-=head2 * starting the package
+=head1 Packaging walkthrough
+
+=head2 starting the package
 
 B<git-import-dsc> is used to introduce the source of a package into the Git
 repository. It operates on the C<.dsc> file and the associated source files. It
@@ -47,14 +47,14 @@
 repository, repeat the last command for all C<.dsc> files you have, in
 incremental version order.
 
-=head2 * cloning existing package repository
+=head2 cloning existing package repository
 
 This can be done with plain L<git-clone(1)>, but using gbp-clone will setup
 tracking branches for upstream sources and pristine-tar data:
 
     $ gbp-clone --pristine-tar ssh://git.debian.org/git/pkg-perl/packages/libfoo-perl.git
 
-=head2 * repository layout
+=head2 repository layout
 
 Upstream sources are kept (in plain, uncompressed form) in the C<upstream>
 branch. The original source tarballs are kept with the help of the
@@ -66,7 +66,7 @@
 debian/changelog with each commit, others leave this to the L<git-dch(1)> tool
 at package release time.
 
-=head2 * pushing to git.debian.org
+=head2 pushing to git.debian.org
 
 Before pushing to git.debian.org for the first time, an empty repository needs
 to be created there. To do this, use the B<setup-repository> script available
@@ -94,7 +94,7 @@
 
 The C<--set-upstream> option helps future use ot C<git pull>.
 
-=head2 * building the package
+=head2 building the package
 
 Use your favourite way of building the Debian package. If the source tarball is
 not in ../, check it out from the pristine-tar info:
@@ -113,7 +113,7 @@
     $ git push
     $ git push --tags
 
-=head2 * upgrading to a new upstream release
+=head2 upgrading to a new upstream release
 
 First make sure that the local repository is up to date, for example using
 L<gbp-pull(1)>.
@@ -149,7 +149,7 @@
  $ git push --all
  $ git push --tags
 
-=head2 * patches
+=head2 patches
 
 L<quilt(1)> does a fine job managing patches, especially if using the C<3.0 
 (quilt)> source format. See L<http://pkg-perl.alioth.debian.org/howto/quilt.html>