This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template.
-- Eric S. Raymond
Problems with winedbg.1:
Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations.
--- winedbg.1-unpatched 2014-06-02 09:40:08.604693388 -0400 +++ winedbg.1 2014-06-02 09:41:09.350110336 -0400 @@ -163,7 +163,7 @@ .IP \fBbreak\ \fIN\fR Adds a breakpoint at line \fIN\fR of current source file. .IP \fBbreak\fR -Adds a breakpoint at current \f$PC\fR address. +Adds a breakpoint at current \fB$PC\fR address. .IP \fBwatch\ *\ \fIN\fR Adds a watch command (on write) at address \fIN\fR (on 4 bytes). .IP \fBwatch\ \fIid\fR
Problems with msiexec.1:
Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations.
--- msiexec.1-unpatched 2014-06-02 17:15:58.428528019 -0400 +++ msiexec.1 2014-06-02 17:18:59.360645276 -0400 @@ -24,25 +24,25 @@ \fR[\fBp\fR|\fBo\fR|\fBe\fR|\fBd\fR|\fBc\fR|\fBa\fR|\fBu\fR|\fBm\fR|\fBs\fR|\fBv\fR]\ \ \fR{\fIpackage\fR|\fIproductcode\fR} Repair an installation. Default options are 'omus' -.IP "\flp\fR" +.IP "\fBlp\fR" Reinstall the file if it is missing. -.IP "\flo\fR" +.IP "\fBlo\fR" Reinstall the file if it is missing or if any older version is installed. -.IP "\fle\fR" +.IP "\fBle\fR" Reinstall the file if it is missing, or if the installed version is equal or older. -.IP "\fld\fR" +.IP "\fBld\fR" Reinstall the file if it is missing or a different version is installed. -.IP "\flc\fR" +.IP "\fBlc\fR" Reinstall the file if it is missing or the checksum does not match. -.IP "\fla\fR" +.IP "\fBla\fR" Reinstall all files. -.IP "\flu\fR" +.IP "\fBlu\fR" Rewrite all required user registry entries. -.IP "\flm\fR" +.IP "\fBlm\fR" Rewrite all required machine registry entries. -.IP "\fls\fR" +.IP "\fBls\fR" Overwrite any conflicting shortcuts. -.IP "\flv\fR" +.IP "\fBlv\fR" Recache the local installation package from the source installation package. .SH PATCHING .IP \fB/p\ \fR{\fIpatch\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] @@ -65,35 +65,35 @@ [\fBi\fR|\fBw\fR|\fBe\fR|\fBa\fR|\fBr\fR|\fBu\fR|\fBc\fR|\fBm\fR|\fBo\fR|\fBp\fR|\fBv\fR]\ [\fB+\fR|\fB!\fR]\ {\fIlogfile\fR} Enable logging to \fIlogfile\fR. Defaults are 'iwearmo'. -.IP "\fl*\fR" +.IP "\fBl*\fR" Enable all logging options except 'v' and 'x'. -.IP "\fli\fR" +.IP "\fBli\fR" Log status messages. -.IP "\flw\fR" +.IP "\fBlw\fR" Log nonfatal warnings. -.IP "\fle\fR" +.IP "\fBle\fR" Log all error messages. -.IP "\fla\fR" +.IP "\fBla\fR" Log start of actions. -.IP "\flr\fR" +.IP "\fBlr\fR" Log action specifc records. -.IP "\flu\fR" +.IP "\fBlu\fR" Log user requests. -.IP "\flc\fR" +.IP "\fBlc\fR" Log initial UI parameters. -.IP "\flm\fR" +.IP "\fBlm\fR" Log out of memory errors. -.IP "\flo\fR" +.IP "\fBlo\fR" Log out of diskspace messages. -.IP "\flp \fR" +.IP "\fBlp \fR" Log terminal properties. -.IP "\flv \fR" +.IP "\fBlv \fR" Verbose logging. -.IP "\flx \fR" +.IP "\fBlx \fR" Log extra debugging messages. -.IP "\fl+ \fR" +.IP "\fBl+ \fR" Append logging to existing file. -.IP "\fl! \fR" +.IP "\fBl! \fR" Flush each line to log. .SH OTHER OPTIONS .IP \fB/h
Problems with winemaker.1:
Unbalanced group in command synopis. You probably forgot to open or close a [ ] or { } group properly.
--- winemaker.1-unpatched 2014-06-02 09:52:02.517334795 -0400 +++ winemaker.1 2014-06-02 09:54:21.272566508 -0400 @@ -29,7 +29,6 @@ .br [ .BR "--generated-files " "] [ " "--nogenerated-files " "] -] .br [ .BR "--wine32 " "]
On 02/29/2016 12:35 PM, esr@thyrsus.com wrote:
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template.
-- Eric S. Raymond
Hi Eric,
the Wine project usually expects "git format-patch"-patches at wine-patches@winehq.org (subscribers only), see https://wiki.winehq.org/Submitting_Patches.
Greets jre
Jens Reyer jre.winesim@gmail.com:
On 02/29/2016 12:35 PM, esr@thyrsus.com wrote:
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template.
-- Eric S. Raymond
Hi Eric,
the Wine project usually expects "git format-patch"-patches at wine-patches@winehq.org (subscribers only), see https://wiki.winehq.org/Submitting_Patches.
Greets jre
You clearly don't understand the implications of what you're asking.
I'm trying to get the *entire* manual page corpus cleaned up to the point where it can easily be HTMLized and cross-indexed. It's a huge job; I've been plugging at it for twelve years. I'm tracking over 500 man-page bugs on hundreds of separate projects and have 327 patches pending.
I don't have the time or bandwidth to become a mailing-list subscriber and adapt to every single local set of submission conventions. This work is nearly too difficult for a single human as it is, and nobody else is signing up to do it.
It's as much as I can do to provide fixes. I need project maintainers to be helpful and take responsibility for doing the mechanics of applying them, or I won't be able to get this done at all.
On 03/01/2016 09:05 PM, Eric S. Raymond wrote:
Jens Reyer jre.winesim@gmail.com:
On 02/29/2016 12:35 PM, esr@thyrsus.com wrote:
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template.
-- Eric S. Raymond
Hi Eric,
the Wine project usually expects "git format-patch"-patches at wine-patches@winehq.org (subscribers only), see https://wiki.winehq.org/Submitting_Patches.
Greets jre
You clearly don't understand the implications of what you're asking.
I'm trying to get the *entire* manual page corpus cleaned up to the point where it can easily be HTMLized and cross-indexed. It's a huge job; I've been plugging at it for twelve years. I'm tracking over 500 man-page bugs on hundreds of separate projects and have 327 patches pending.
I don't have the time or bandwidth to become a mailing-list subscriber and adapt to every single local set of submission conventions. This work is nearly too difficult for a single human as it is, and nobody else is signing up to do it.
It's as much as I can do to provide fixes. I need project maintainers to be helpful and take responsibility for doing the mechanics of applying them, or I won't be able to get this done at all.
I fully understand your situation. I am not the maintainer, just a contributor.
Your inital mail might not have been seen at all, however chances are higher with this thread now.
AJ, I might resubmit that for Eric if that helps.
Greets jre