From: "E. Gryaznova" <grev@namesys.com>
To: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: problems in one or more man pages you maintain
Date: Tue, 17 Feb 2004 16:22:49 +0300 [thread overview]
Message-ID: <403215A9.66D25DD2@namesys.com> (raw)
Hello,
This was fixed in reiserfsprogs-3.6.12.
Thanks,
Lena
Eric S. Raymond wrote :
> This is automatically generated email about problems in a man page for
which
> you appear to be responsible. If you are not the right person or
list, tell
> me and I will attempt to correct my database.
> See http://catb.org/~esr/doclifter/problems.html for details on how
and
> why these patches were generated. Feel free to email me with any
questions.
> Note: This patch does not change the mod date of the manual page. You
> may wish to do that by hand.
> Problems with debugreiserfs.8:
> 1. Missing or garbled name section. The most common form of garbling
> is a missing - or extra -. Or your manual page may have been generated
> by a tool that doesn't emit a NAME section as it should. These
> problems make it impossible to lift the page to DocBook. They
> can also confuse some implementations of man -k.
> --- debugreiserfs.8-orig 2003-11-26 19:25:49.000000000 -0500
> +++ debugreiserfs.8 2003-11-26 19:26:25.000000000 -0500
> @@ -3,7 +3,7 @@
> .\"
> .TH DEBUGREISERFS 8 "January 2002" "Reiserfsprogs 3.6.4"
> .SH NAME
> -debugreiserfs
> +debugreiserfs \- debugging tool for the ReiserFS filesystem
> .SH SYNOPSIS
> .B debugreiserfs
> [
> Problems with reiserfstune.8:
> 1. Missing or garbled name section. The most common form of garbling
> is a missing - or extra -. Or your manual page may have been generated
> by a tool that doesn't emit a NAME section as it should. These
> problems make it impossible to lift the page to DocBook. They
> can also confuse some implementations of man -k.
> --- reiserfstune.8 2003-02-16 18:47:41.000000000 -0500
> +++ reiserfstune.8 2003-02-16 18:48:07.000000000 -0500
> @@ -3,7 +3,7 @@
> .\"
> .TH REISERFSTUNE 8 "January 2002" "Reiserfsprogs-3.6.2"
> .SH NAME
> -reiserfstune
> +reiserfstune \- tune parameters of a Reiser file system
> .SH SYNOPSIS
> .B reiserfstune
> [ \fB-f\fR ]
> --
> Eric S. Raymond
next reply other threads:[~2004-02-17 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 13:22 E. Gryaznova [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 6:25 problems in one or more man pages you maintain esr
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Eric S. Raymond
2005-05-19 6:25 ` esr
2004-02-17 5:56 esr
2003-12-09 19:29 esr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403215A9.66D25DD2@namesys.com \
--to=grev@namesys.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.