util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: "Helge Kreutzmann" <debian@helgefjell.de>,
	util-linux@vger.kernel.org,
	"Mario Blättermann" <mario.blaettermann@gmail.com>
Subject: Re: Errors in man pages of util-linux
Date: Mon, 11 May 2020 12:32:08 +0200	[thread overview]
Message-ID: <CAKgNAkgqKs=Q4qvPHirHa6KjW3qOqyyNG7sCxHX2RfWiOBqRbg@mail.gmail.com> (raw)
In-Reply-To: <20200511092734.6izjgahtz37iya6v@ws.net.home>

Hello Karel

On Mon, 11 May 2020 at 11:27, Karel Zak <kzak@redhat.com> wrote:
>
> On Sat, May 09, 2020 at 09:05:50PM +0200, Michael Kerrisk wrote:
> > On Sat, May 9, 2020 at 9:00 PM Helge Kreutzmann <debian@helgefjell.de> wrote:
> > >
> > > Hello Michael,
> > > On Sat, May 09, 2020 at 08:53:31PM +0200, Michael Kerrisk wrote:
> > > > Hello Helge ;-),
>
> Thanks for your report Helge.
>
> > > > I think no maintainer wants to deal with a 1000-line mail listing 100+
> > > > minor bugs. May I suggest making the maintainer's life a little easier
> > > > by breaking things up into pieces. For example, one mail per manual
> > > > page (which would be 43 mails by my count).  But maybe Karel has
> > > > another suggestion on how you could make his life easier.
>
> Well, that's simple, send patches ;-)))

So, I've recently been through this process with Helge for 100+
man-pages bug reports.Here's my experience/summary for what its worth:
* Because of info I have on the project website, Helge sent bug reports
  one per mail, so one day without warning, I got 138 mails :-).
  (My preference really is separate mails for each issue. But I told
  Helge I would have liked a little warning first :-).)

* A large number of the reports just required simple one-line edits that
  could often be done in a minute.
* It was clear that the effort required for Helge to make patches would
  be rather greater than me just doing the one-line edits
* Making patches requires an added layer of work for Helge, since
  he/the translators are working with a mutated version of the source.
  (The flip side of this is that it is occasionally a little tricky to convert
  the text that Helge is sending you back to the corresponding page
  source.)

> > Maybe hold off for a day or three before investing effort on this.
> > Karel may have a better idea than mine re his preferred method of
> > reporting.
>
> I have no another idea (maybe github issue(s), but it will be invisible
> for many contributors).

Have mercy! Please no... :-).

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  parent reply	other threads:[~2020-05-11 10:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 19:13 Errors in man pages of util-linux Helge Kreutzmann
2020-05-09 18:53 ` Michael Kerrisk
2020-05-09 19:00   ` Helge Kreutzmann
2020-05-09 19:05     ` Michael Kerrisk
2020-05-11  9:27       ` Karel Zak
2020-05-11  9:50         ` Helge Kreutzmann
2020-05-11 10:32         ` Michael Kerrisk (man-pages) [this message]
2022-02-10 19:23 Helge Kreutzmann
2022-02-10 20:35 ` Helge Kreutzmann
2022-02-13 18:33   ` Mario Blättermann
2022-02-13 18:51     ` Helge Kreutzmann
2022-02-13 19:35       ` Bill Unruh

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='CAKgNAkgqKs=Q4qvPHirHa6KjW3qOqyyNG7sCxHX2RfWiOBqRbg@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=kzak@redhat.com \
    --cc=mario.blaettermann@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).