Util-Linux Archive on lore.kernel.org
 help / color / Atom feed
From: Karel Zak <kzak@redhat.com>
To: J William Piggott <elseifthen@gmx.com>
Cc: Carlos Santos <unixmania@gmail.com>, util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.35
Date: Mon, 27 Jan 2020 17:13:17 +0100
Message-ID: <20200127161317.wwyupvqbighx3rqx@ws.net.home> (raw)
In-Reply-To: <nycvar.YAK.7.76.2001261131130.3053@zhn.tzk.pbz>

On Sun, Jan 26, 2020 at 11:59:59AM -0500, J William Piggott wrote:
> You do realize that I had to heavily modify that file to remove its
> gnulib dependencies (because you said no to gnulib). If I recall

I know, this is why we keep it in the tree (and thanks for all the

> correctly I had newer and older versions to chose from and picked that
> one due to it having the most bugs fixed while still being practical to
> strip its gnulib dependence.
> The reasons for making the change were:
>  * remove hwclock's dependence on date(1)
>  * remove an insecure call to date(1)
>  * I thought there would be to many complaints if the accepted input
>    date formats were changed
> As to the last bullet point; personally I think having the --date option
> accept every date syntax know to history is nonsense. 

Yes, I agree it's probably overkill.

> Or you could just use the existing utillinux date parser.

This is what I have implemented for --disable-hwclock-gplv3 to have
anything ASAP for the next 2.35.1 update... Maybe we can make it the
default for the next release v2.36 and later remove the gnulib code at

> The question is, do you want to deal with any pushback for
> changing the long established accepted --date formats?

IMHO the existing utillinux date parser is good enough, but I have no
clue how people use --date.


 Karel Zak  <kzak@redhat.com>

  parent reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 10:57 Karel Zak
2020-01-24 19:16 ` Carlos Santos
2020-01-25 10:51   ` Karel Zak
2020-01-25 11:19     ` Carlos Santos
2020-01-26 16:59     ` J William Piggott
2020-01-26 17:50       ` Carlos Santos
2020-01-27 16:13       ` Karel Zak [this message]
2020-01-27 16:38         ` Carlos Santos
2020-01-27 20:18           ` Karel Zak
2020-01-27 13:34   ` Karel Zak
2020-01-27 13:40     ` Karel Zak
2020-01-27 15:25       ` Karel Zak
2020-01-27 16:29       ` Carlos Santos
2020-01-27 20:21         ` Karel Zak
2020-01-28 19:24           ` Sami Kerola
2020-01-30 11:17             ` Karel Zak

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200127161317.wwyupvqbighx3rqx@ws.net.home \
    --to=kzak@redhat.com \
    --cc=elseifthen@gmx.com \
    --cc=unixmania@gmail.com \
    --cc=util-linux@vger.kernel.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Util-Linux Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/util-linux/0 util-linux/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 util-linux util-linux/ https://lore.kernel.org/util-linux \
	public-inbox-index util-linux

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git