From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: On bug bombing
Date: Fri, 1 May 2020 10:34:22 +0200 [thread overview]
Message-ID: <CAKgNAkhb0HGsZy2Upgn-_Qui60vo62JV_v0jdhPf54wTQh5wYA@mail.gmail.com> (raw)
In-Reply-To: <20200501072055.GC938@Debian-50-lenny-64-minimal>
Hello Helge,
On Fri, 1 May 2020 at 09:20, Helge Kreutzmann <debian@helgefjell.de> wrote:
>
> 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.
Time is always in short supply :-}. And sometime, when I queue things,
they just get lost (for ever, or for a long 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.
I figured that the story must be something like this. So, in any case,
thank you that you did the work. It is appreciated.
> 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.
Yes. Individual reports is best. That way, I can accept/reject/discuss
each issue individually.
> 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.
I do suggest at least warnin the upstream that a lot of reports are
about to land...
> 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.
You're welcome!
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-05-01 8:34 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
2020-05-01 8:34 ` Michael Kerrisk (man-pages) [this message]
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=CAKgNAkhb0HGsZy2Upgn-_Qui60vo62JV_v0jdhPf54wTQh5wYA@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@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).