From: Karel Zak <kzak@redhat.com>
To: J William Piggott <elseifthen@gmx.com>
Cc: Benno Schulenberg <bensberg@justemail.net>,
Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 3/5] hwclock: remove depreciated ntpdate
Date: Tue, 17 Mar 2015 10:29:01 +0100 [thread overview]
Message-ID: <20150317092901.GS28925@ws.net.home> (raw)
In-Reply-To: <5507A187.2020303@gmx.com>
On Mon, Mar 16, 2015 at 11:37:43PM -0400, J William Piggott wrote:
> On 03/16/2015 06:33 AM, Karel Zak wrote:
> > On Sun, Mar 15, 2015 at 04:26:45PM +0100, Benno Schulenberg wrote:
> >>
> >> On Fri, Mar 13, 2015, at 20:18, J William Piggott wrote:
> >>> Replace references to the depreciated ntpdate with sntp.
> >>
> >> s/depreciated/deprecated/
> >>
> >>> -.BR \%ntpdate\ \-q " , or " \%date\ \-Ins
> >>> +.BR \%sntp ", or " \%date\ \-Ins
> >>
> >> Hmm, maybe it's a bit to early to delete the mention of ntpdate?
> >> My fairly recent Linux Mint doesn't have sntp yet. Maybe add
> >> sntp to the list instead of replacing ntpdate?
> >
> > Good point, it would be better to use something like "ntpdate or more
> > recent sntp".
>
> No, it is not a good point. I assume he means *too* early, that's the
> funniest thing I've heard all day. No wait, "doesn't have sntp yet",
> that's the funniest thing I've heard all day.
>
> The sntp client and ntpdate are both from the same project and
> approximately the same age. Nobody was interested in maintaining ntpdate
> so it *depreciated* over many years before being officially *deprecated*
> by the project.
You miss the point, after util-linux update, someone will read the man
page and then type "sntp" on command line, but because he has old /
stupid distro it will be unsuccessful. What next if there is no any
pointer to any other alternative?
You're absolutely right with ntpdate vs. sntp, but it seems reality is
so painful that people still have systems where is no sntp.
> Before I added ntpdate two months ago, the hwclock man-page had gone 20
> years without it. Now there's concern over removing it?
OK :-) I'm going to apply the patches, it's nothing critical.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-03-17 9:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 19:11 [PATCH 1/5] hwclock: add TZDIR J William Piggott
2015-03-13 19:15 ` [PATCH 2/5] hwclock: Improve FILES section J William Piggott
2015-03-13 19:18 ` [PATCH 3/5] hwclock: remove depreciated ntpdate J William Piggott
2015-03-15 15:26 ` Benno Schulenberg
2015-03-16 0:19 ` Isaac Dunham
2015-03-16 10:33 ` Karel Zak
2015-03-17 3:37 ` J William Piggott
2015-03-17 9:29 ` Karel Zak [this message]
2015-03-17 21:10 ` J William Piggott
2015-03-13 19:22 ` [PATCH 4/5] hwclock: add '11 minute mode' information J William Piggott
2015-03-15 15:47 ` Benno Schulenberg
2015-03-17 9:57 ` Karel Zak
2015-03-18 1:16 ` J William Piggott
2015-03-18 9:43 ` Karel Zak
2015-03-13 19:26 ` [PATCH 5/5] hwclock: man-page errata J William Piggott
2015-03-15 15:51 ` Benno Schulenberg
2015-03-15 15:20 ` [PATCH 1/5] hwclock: add TZDIR Benno Schulenberg
2015-03-16 10:30 ` Karel Zak
2015-03-17 9:58 ` Karel Zak
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=20150317092901.GS28925@ws.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=elseifthen@gmx.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