r65993 - /website/git.pod

[ghedo-guest at users.alioth.debian.org]

Author: ghedo-guest
Date: Sun Dec 19 14:50:50 2010
New Revision: 65993

URL: http://svn.debian.org/wsvn/?sc=1&rev=65993
Log:
fix various typos

Modified:
    website/git.pod

Modified: website/git.pod
URL: http://svn.debian.org/wsvn/website/git.pod?rev=65993&op=diff
==============================================================================
--- website/git.pod (original)
+++ website/git.pod Sun Dec 19 14:50:50 2010
@@ -52,9 +52,9 @@
 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 ssh://git.debian.org/git/pkg-perl/packages/libfoo-perl.git
+    $ gbp-clone --pristine-tar ssh://git.debian.org/git/pkg-perl/packages/libfoo-perl.git
 
-=head2 * repossitory 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
@@ -130,7 +130,7 @@
 
 Then import the new upstream release in the git repository:
 
- $ git-import-orig --pritine-tar ../libfoo-bar-perl_2.00_orig.tar.gz
+ $ git-import-orig --pristine-tar ../libfoo-bar-perl_2.00_orig.tar.gz
 
 This will import the new sources in the C<upstream> branch, update tarball info
 in the C<pristine-tar> branch, tag the upstream release and finally merge that
@@ -142,7 +142,7 @@
 
 This combines the previous two steps in a single command.
 
- $ debcommit -a -m'new upsream release 2.00'
+ $ debcommit -a -m'new upstream release 2.00'
 
 Don't forget to share your work when ready:
 
@@ -151,15 +151,15 @@
 
 =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>
+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>
 for a guide. L<gbp-pq(1)> can be used for treating the patches as a series of
 commits. See
 L<https://honk.sigxcpu.org/piki/development/debian_packages_in_git/>
 
 =head1 TIPS & TRICKS
 
-L<git-buildpackage(1)> has a configuration file whch can save some typing on
+L<git-buildpackage(1)> has a configuration file which can save some typing on
 each command. The C<pristine-tar> option is particularly handy.
 
 =head1 CAVEATS