linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: On bug bombing
Date: Fri, 1 May 2020 09:20:55 +0200	[thread overview]
Message-ID: <20200501072055.GC938@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <62162aec-6dfa-18b9-b370-00d772f3e7b7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]

Hello Michael,
On Mon, Apr 20, 2020 at 12:26:41PM +0200, Michael Kerrisk (man-pages) wrote:
> I am torn between saying thank you for all the effort you
> clearly made and saying PLEASE DON'T DO THIS!

Ok.

> Submitting one hundred plus bug reports at the same time
> is _very_ burdensome for an upstream maintainer. Honestly,
> if it had not been for lockdown, I might simply have ignored
> the whole series of mails.

That would have been a pitty.

I would have assumed that you process them at your convenience, i.e.
each when you have time.

> In the future, please do not wait for  huge backlog to build up
> before sending me reports. (10 reports at a time is fine; 100, 
> not so much.)

Well, in the past (i.e. 10 years) we (german) translators always said
"we should report this". But "we" always amounted to no one doing it.
We were only recording issues found. So I finally decided to proceed. 

Since you are our biggest upstream, I started with your pages.
Intially I would have made one big bug report, but I understood this
is not requested from your side. 

Since it was mostly script based (and I was working on the scripts
while preparing) they came in all at once. I could have added a
throttle, like 10 / day, of course.

I'm still learning the process(es), so the next upstream might get a
better experience and I apologize for all the glitches I made.

Anyhow, I hope to report more frequent (and with much lower numbers) in
the future.

> In any case, thank you very much for your many reports.

Thanks from my side that you accepted and processed them.

Greetings

          Helge
-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-01  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  6:48 Errors in man pages, here: mount_namespaces(7): Understanding Helge Kreutzmann
2020-04-20 10:14 ` Michael Kerrisk (man-pages)
2020-04-20 10:26 ` On bug bombing Michael Kerrisk (man-pages)
2020-05-01  7:20   ` Helge Kreutzmann [this message]
2020-05-01  8:34     ` Michael Kerrisk (man-pages)

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=20200501072055.GC938@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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 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).