From: Carlos Santos <unixmania@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.35
Date: Fri, 24 Jan 2020 16:16:47 -0300 [thread overview]
Message-ID: <CAJ4jsadjw3xXbrqjsB9cwv_iwodfHWJ4CnhD4oXW_Lvwh0W8XQ@mail.gmail.com> (raw)
In-Reply-To: <20200121105711.zzeeolydlivqnik7@ws.net.home>
Hi Karel,
On Tue, Jan 21, 2020 at 7:59 AM Karel Zak <kzak@redhat.com> wrote:
>
>
> The util-linux release v2.35 is available at
>
> http://www.kernel.org/pub/linux/utils/util-linux/v2.35/
>
> Feedback and bug reports, as always, are welcomed.
>
> Karel
>
That's great. Thanks!
--8<--
> Changes between v2.34 and v2.35
> -------------------------------
--8<--
> docs:
> - Fix adjtime documentation [Pierre Labastie]
> - add GPLv3 text [Karel Zak]
That's a problem. It makes hwclock hard to include in embedded systems
due to the GPLv3 restrictions.
I noticed that it comes due to sys-utils/hwclock-parse-date.y, which
was taken from gnulib. Would it be possible to take the file from an
previous version of gnulib that was still under GPLv2?
An alternative approach would be porting a similar code using a more
liberal license, e.g. BSD.
What do you think?
--
Carlos Santos <unixmania@gmail.com>
next prev parent reply other threads:[~2020-01-24 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 10:57 [ANNOUNCE] util-linux v2.35 Karel Zak
2020-01-24 19:16 ` Carlos Santos [this message]
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
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 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=CAJ4jsadjw3xXbrqjsB9cwv_iwodfHWJ4CnhD4oXW_Lvwh0W8XQ@mail.gmail.com \
--to=unixmania@gmail.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).