Problems in winedbg.1, msiexec.1, winemaker.1
Eric S. Raymond
esr at thyrsus.com
Tue Mar 1 14:05:49 CST 2016
Jens Reyer <jre.winesim at gmail.com>:
> On 02/29/2016 12:35 PM, esr at 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 at 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.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
More information about the wine-devel
mailing list