From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Karel Zak <kzak@redhat.com>
Cc: Carlos Santos <casantos@datacom.com.br>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: [ANNOUNCE] util-linux v2.33
Date: Wed, 7 Nov 2018 11:02:21 +0100 [thread overview]
Message-ID: <20181107100221.ie4f4oxx7kq32xm7@function> (raw)
In-Reply-To: <20181107094956.ad56ai463xu262u5@ws.net.home>
Karel Zak, le mer. 07 nov. 2018 10:49:56 +0100, a ecrit:
> On Tue, Nov 06, 2018 at 11:20:08PM -0200, Carlos Santos wrote:
> > > From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
> > > To: "Karel Zak" <kzak@redhat.com>
> > > Cc: "util-linux" <util-linux@vger.kernel.org>
> > > Sent: Terça-feira, 6 de novembro de 2018 10:34:02
> > > Subject: Re: [ANNOUNCE] util-linux v2.33
> >
> > > Hello,
> > >
> > > Karel Zak, le mar. 06 nov. 2018 12:33:06 +0100, a ecrit:
> > >> The util-linux release v2.33 is available at
> > >>
> > >> http://www.kernel.org/pub/linux/utils/util-linux/v2.33
> > >>
> > >> Feedback and bug reports, as always, are welcomed.
> > >
> > > It seems new portability issues came in since the rc I tested :)
> > > Fix attached.
> > >
> > > Samuel
> >
> > Could you please explain what portability issues your patch fixes?
>
> The reload agetty feature depends on inotify (netlink, ....). I guess
> it's unsupported by GNU Hurd.
Yes, and the #ifdef AGETTY_RELOAD are incoherent: issue_is_changed
accesses fields which are not defined when AGETTY_RELOAD is not defined,
and no_reload is used in pieces of code where AGETTY_RELOAD is not
defined.
Samuel
next prev parent reply other threads:[~2018-11-07 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 11:33 [ANNOUNCE] util-linux v2.33 Karel Zak
2018-11-06 12:34 ` Samuel Thibault
2018-11-07 1:20 ` Carlos Santos
2018-11-07 9:49 ` Karel Zak
2018-11-07 10:02 ` Samuel Thibault [this message]
2018-11-12 10:39 ` Karel Zak
2018-11-07 12:42 ` Christian Hesse
2018-11-07 12:55 ` [PATCH 1/1] agetty: fix output of escaped characters Christian Hesse
2018-11-07 13:19 ` Karel Zak
2018-11-12 10:39 ` 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=20181107100221.ie4f4oxx7kq32xm7@function \
--to=samuel.thibault@ens-lyon.org \
--cc=casantos@datacom.com.br \
--cc=kzak@redhat.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).