From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: J William Piggott <elseifthen@gmx.com>, util-linux@vger.kernel.org
Subject: Re: pull: hwclock 27 changes
Date: Mon, 9 Jan 2017 12:32:37 +0100 [thread overview]
Message-ID: <20170109113201.kt3mmxr7fqlwscdm@ws.net.home> (raw)
In-Reply-To: <alpine.LNX.2.20.1701072212010.9096@imuri>
On Sat, Jan 07, 2017 at 11:06:23PM +0000, Sami Kerola wrote:
> > >
> > >
> > > I tried to convince Karel of this long ago. This code has been broken
> > > from day one, so nobody can be using it. IMO, it should be removed now.
> > >
> > >
>
> I agree. --compare is broken. I think there are couple options.
>
> 1) remove --compare code, and mention in manual page it's gone
> 2) keep the code, but deprecate it
> 3) keep the code, and fix it (but how???)
> 4) keep the broken code and whistle happy days theme song
> 5) something else
>
> I am 60-40 leaning towards recommending removal. If we don't remove rest
> of my 40 goes to deprecate. Karel, I think we need maintainer advice.
I have re-read our old discussions about this topic and I agree that
it's better to kill the problematic (broken?) functionality that care
about backward compatibility. It really seems nobody uses this stuff.
So, go ahead and send patch to remove all around --compare.
BTW, we had discussion about unmaintained adjtimex merge to
util-linux.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-01-09 11:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 21:41 pull: hwclock 27 changes Sami Kerola
2017-01-03 14:34 ` J William Piggott
[not found] ` <05e4405f-8096-9261-f9f2-d2c6b84675bc@gmx.com>
2017-01-07 19:37 ` J William Piggott
2017-01-07 20:32 ` J William Piggott
2017-01-07 23:06 ` Sami Kerola
2017-01-08 9:39 ` Sami Kerola
2017-01-08 21:21 ` J William Piggott
2017-01-08 10:09 ` Sami Kerola
2017-01-08 21:21 ` J William Piggott
2017-01-08 21:21 ` J William Piggott
2017-01-11 21:44 ` Sami Kerola
2017-01-13 1:30 ` J William Piggott
2017-01-14 9:34 ` Sami Kerola
2017-01-14 22:51 ` J William Piggott
2017-01-22 19:03 ` J William Piggott
2017-01-25 21:54 ` Sami Kerola
2017-01-27 2:07 ` J William Piggott
2017-02-02 15:04 ` [ping] Karel: " J William Piggott
2017-02-03 22:41 ` Sami Kerola
2017-02-11 17:10 ` J William Piggott
2017-02-04 18:47 ` Karel Zak
2017-02-05 22:37 ` Sami Kerola
2017-02-09 10:43 ` Karel Zak
2017-02-09 11:09 ` Karel Zak
2017-02-11 17:10 ` J William Piggott
2017-01-09 11:32 ` Karel Zak [this message]
2017-01-09 13:53 ` J William Piggott
2017-01-09 20:48 ` Bjarni Ingi Gislason
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=20170109113201.kt3mmxr7fqlwscdm@ws.net.home \
--to=kzak@redhat.com \
--cc=elseifthen@gmx.com \
--cc=kerolasa@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.