On Fri, Jul 23, 2010 at 04:48:41AM +0200, Florian Ragwitz wrote: > =for is just for one paragraph, not until the next command or anything like > that. > --- > pod/perlrepository.pod | 1 - > 1 files changed, 0 insertions(+), 1 deletions(-) > > diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod > index 7cf75e9..58ff18a 100644 > --- a/pod/perlrepository.pod > +++ b/pod/perlrepository.pod > @@ -429,7 +429,6 @@ immediately after the source-changes that caused them, so as to have > as little effect as possible on the bisectability of your patchset. > > =for XXX > - > What should we recommend about binary files now? Do we need anything? > > =head2 Getting your patch accepted > -- > 1.7.1 It seems that you applied this as commit 6a3d1e7ec946e959, fixing my Pod formatting mess up introduced with commit 6e2cec711386bcf5. (The file perlrepository.pod has subsequently been eliminated a part of commit 04c692a854b61dfa). So this thread has closure :-) Nicholas ClarkThread Previous