util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: util-linux@vger.kernel.org,
	"Mario Blättermann" <mario.blaettermann@gmail.com>,
	"Karel Zak" <kzak@redhat.com>,
	"Michael Kerrisk-manpages" <mtk.manpages@gmail.com>
Subject: Re: Errors in man pages of util-linux
Date: Sat, 9 May 2020 21:05:50 +0200	[thread overview]
Message-ID: <CALxWeYpxvs+fcXzbExJ0n5ebeFtBdzm53ucPndW475CKe2KR0Q@mail.gmail.com> (raw)
In-Reply-To: <20200509190020.GA28852@Debian-50-lenny-64-minimal>

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 ;-),
> >
> > 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.
>
> Sure, I can do this, it did not see this mentioned for reporting bugs
> in util-linux, hence I did not do so.
>
> Will do so soon, probably tomorrow.

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.

Thanks,

Michael

  reply	other threads:[~2020-05-09 19:06 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 [this message]
2020-05-11  9:27       ` Karel Zak
2020-05-11  9:50         ` Helge Kreutzmann
2020-05-11 10:32         ` Michael Kerrisk (man-pages)
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=CALxWeYpxvs+fcXzbExJ0n5ebeFtBdzm53ucPndW475CKe2KR0Q@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).