r35206 - /website/howto/quilt.pod

[gregoa at users.alioth.debian.org]

Author: gregoa
Date: Mon May 11 17:55:24 2009
New Revision: 35206

URL: http://svn.debian.org/wsvn/?sc=1&rev=35206
Log:
replace C<> with F<> where file names are formatted

Modified:
    website/howto/quilt.pod

Modified: website/howto/quilt.pod
URL: http://svn.debian.org/wsvn/website/howto/quilt.pod?rev=35206&op=diff
==============================================================================
--- website/howto/quilt.pod (original)
+++ website/howto/quilt.pod Mon May 11 17:55:24 2009
@@ -15,13 +15,13 @@
 C<quilt> helps managing a series of patches that a debian package maintainer
 needs applied to upstream source when building the package. It is similar to
 C<dpatch> and C<cdbs>'s simple-patchsys in that the patches are kept as a
-series of files in C<debian/patches>.
+series of files in F<debian/patches>.
 
 =head2 1.0. Preparation
 
 C<quilt> uses a special directory for keeping patches (not very surprising).
-Unfortunatelly, that directory is C<./patches/> by default. For Debian packages
-C<./debian/patches/> is far more comfortable. To flawlessly fix this, add
+Unfortunatelly, that directory is F<./patches/> by default. For Debian packages
+F<./debian/patches/> is far more comfortable. To flawlessly fix this, add
 C<export QUILT_PATCHES=debian/patches> in your shell resource file and reload
 it. This way you won't have to worry about this quilt oddity (like me; even
 forgot to mention it in the first revision of this document).
@@ -34,7 +34,7 @@
 C<quilt> manages the series of patches as a stack. You push to it (apply a
 patch) and pop from it (unapply a patch).
 
-There's one special file in C<debian/patches>, C<series>, which contains the
+There's one special file, F<debian/patches/series>, which contains the
 list of all patches to be applied. C<quilt> applies patches in the order they
 are listed in that file.
 
@@ -70,7 +70,7 @@
 To create a patch, run C<quilt new $patch_name>. If you want C<.patch>
 extension, you need to give it.
 
-This will create a new patch entry in C<debian/patches>. This patch also
+This will create a new patch entry in F<debian/patches>. This patch also
 becomes the I<topmost> or current patch. This is the patch that is at the top
 of the stack.
 
@@ -83,7 +83,7 @@
 
 When you're finished, run C<quilt refresh>. This will compare the noted state
 of the edited files with their present state and produce a patch in
-C<debian/patches>.
+F<debian/patches>.
 
 Note that that patch is currently applied. Check it with C<quilt applied>.
 
@@ -117,8 +117,8 @@
 
 =head2 3.1 The "classical" way
 
-C<include /usr/share/quilt/quilt.make> has some candy for C<debian/rules>.
-First, it defines C<QUILT_PATCHES> to be C<debian/patches> so that one doesn't
+C<include /usr/share/quilt/quilt.make> has some candy for F<debian/rules>.
+First, it defines C<QUILT_PATCHES> to be F<debian/patches> so that one doesn't
 have to worry about that setting in the pbuilder chroot.
 
 Second, it defines C<QUILT_STAMPFN>, which can be used as a C<build-stamp> or
@@ -126,7 +126,7 @@
 
 Lastly, C<unpatch> target is useful as a C<clean> dependency.
 
-Here's a sample fragment from C<debian/rules>:
+Here's a sample fragment from F<debian/rules>:
 
     include /usr/share/quilt/quilt.make
 
@@ -147,7 +147,7 @@
 can fail if parallel build is allowed via C<-jN>. C<patch> and C<build-stamp>
 would be run in parallel, possibly failing due to partly applied patches.
 
-N.B. C</usr/share/quilt/quilt.make> is available since C<quilt> version 0.40.
+N.B. F</usr/share/quilt/quilt.make> is available since C<quilt> version 0.40.
 You are advised to make the quilt build-dependency versioned.
 
 =head2 3.2 The "modern" way
@@ -161,7 +161,7 @@
         dh --with quilt $@
 
 Alternatively C<dh_quilt_patch> and C<dh_quilt_unpatch> can be added to
-C<debian/rules>.
+F<debian/rules>.
 
 For the details take a look at F</usr/share/doc/quilt/README.Debian> and/or
 C<dh_quilt_patch(1)>, C<dh_quilt_unpatch(1)>.