util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.33
Date: Wed, 7 Nov 2018 13:42:17 +0100	[thread overview]
Message-ID: <20181107134217.2fe72a87@leda> (raw)
In-Reply-To: <20181106113306.hd2qcvbde22cxur6@ws.net.home>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

Karel Zak <kzak@redhat.com> on Tue, 2018/11/06 12:33:
> 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.

This breaks printing of (escaped) backslash in /etc/issue. We have
a downstream bug report in Arch Linux bugtracker [0] including issue file
that triggers the behaviour. The bad commit is 6522d88d [1].

[0] https://bugs.archlinux.org/task/60731
[1]
https://github.com/karelzak/util-linux/commit/6522d88d08ffbba528e15ab4e081fb2846bac03d
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-11-07 12:50 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
2018-11-12 10:39   ` Karel Zak
2018-11-07 12:42 ` Christian Hesse [this message]
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=20181107134217.2fe72a87@leda \
    --to=list@eworm.de \
    --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).