Use C<< >> to avoid tripping a podchecker heuristic for "don't you mean F<>?"
authorNicholas Clark <nick@ccl4.org>
Sun, 3 Jul 2011 14:33:54 +0000 (16:33 +0200)
committerNicholas Clark <nick@ccl4.org>
Sun, 3 Jul 2011 14:33:54 +0000 (16:33 +0200)
In this case, commiters/somework is not a file, hence C<> is correct.

pod/perlgit.pod

index de1fecf..0e855fa 100644 (file)
@@ -730,7 +730,7 @@ branches and rewriting history>, which you should regularly rebase
 against blead to ensure that your code is not broken by blead moving.
 When you have finished your work and performed a final rebase and test,
 you can merge it into master like this (assuming your work was on the
-branch C<committer/somework>):
+branch C<<committer/somework>>):
 
   $ git checkout blead
   $ git merge --no-ff --no-commit committer/somework