From: Karel Zak <kzak@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "Michael Kerrisk" <mtk.manpages@gmail.com>,
"Helge Kreutzmann" <debian@helgefjell.de>,
util-linux@vger.kernel.org,
"Mario Blättermann" <mario.blaettermann@gmail.com>
Subject: Re: Errors in util-linux man pages, here: adjtime_config.5: Wording
Date: Fri, 15 May 2020 09:50:03 +0200 [thread overview]
Message-ID: <20200515075003.szuxgob6qy63imva@ws.net.home> (raw)
In-Reply-To: <fa40b05f-7050-c5ee-a0ea-5af2d104a1bc@physik.fu-berlin.de>
On Thu, May 14, 2020 at 10:15:47PM +0200, John Paul Adrian Glaubitz wrote:
> On 5/14/20 10:09 PM, Michael Kerrisk wrote:
> >> On 5/14/20 8:51 PM, Helge Kreutzmann wrote:
> >>> I'm now reporting the errors for your project. If future reports should
> >>> use another channel, please let me know.
> >>
> >> I think you should send your changes as patches, preferably with a git pull
> >> request as the current form of submitting these changes requires a lot of
> >> manual editing due to the large number of changes involved.
> >
> > Well, yes, but see
> > https://lore.kernel.org/util-linux/CAKgNAkgqKs=Q4qvPHirHa6KjW3qOqyyNG7sCxHX2RfWiOBqRbg@mail.gmail.com/
>
> Doesn't convince, me really. I don't think it's too much to ask for to
> read the documentation of git and then create a set of patches.
Helge's way provides opportunity for other mailing list members to
contribute :-)
> I wouldn't accept such mass mails for my own projects, it's just way too
> much work to import all these changes manually. And I also haven't seen
> any other project do that in the past 20 years, so I'm not sure how successful
> this strategy is.
Sharing is caring ... better report bugs than ignore.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-05-15 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:51 Errors in util-linux man pages, here: adjtime_config.5: Wording Helge Kreutzmann
2020-05-14 19:20 ` John Paul Adrian Glaubitz
2020-05-14 19:42 ` Helge Kreutzmann
2020-05-14 19:46 ` John Paul Adrian Glaubitz
2020-05-14 20:09 ` Michael Kerrisk
2020-05-14 20:15 ` John Paul Adrian Glaubitz
2020-05-14 20:33 ` Michael Kerrisk (man-pages)
2020-05-15 7:50 ` Karel Zak [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=20200515075003.szuxgob6qy63imva@ws.net.home \
--to=kzak@redhat.com \
--cc=debian@helgefjell.de \
--cc=glaubitz@physik.fu-berlin.de \
--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).