util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: Karel Zak <kzak@redhat.com>
Cc: "Michael Kerrisk" <mtk.manpages@gmail.com>,
	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 11:50:55 +0200	[thread overview]
Message-ID: <20200511095055.GA16591@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <20200511092734.6izjgahtz37iya6v@ws.net.home>

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

Hello Karel,
On Mon, May 11, 2020 at 11:27:34AM +0200, Karel Zak 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:
> > > 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 ;-)))
> 
> > > 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.
> 
> I think Michael is right. If we will split it then more volunteers can 
> work on it and it will be more easy to maintain all the task.

Right, will do so, but due to other commitments it might take a few
days (hopefully faster).

Also Mario has send me privately some suggestions for fixing which I
will integrate.

> > 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).

I personally prefer a mail interface and not yet another account, so
I'll send the issues the the recipients of this e-mail soon.

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-11  9:51 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 [this message]
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=20200511095055.GA16591@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=kzak@redhat.com \
    --cc=mario.blaettermann@gmail.com \
    --cc=mtk.manpages@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).