From: Carlos Santos <casantos@datacom.com.br>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: [ANNOUNCE] util-linux v2.33
Date: Tue, 6 Nov 2018 23:20:08 -0200 (BRST) [thread overview]
Message-ID: <987477353.537443.1541553608738.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20181106123402.cy52t2ql4yvfqme6@function>
> 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?
Also, could you re-generate the patch with git format-patch and add
a Signed-off-by line, so I can use it in the Buildroot package?
Thanks in advance.
--
Carlos Santos (Casantos) - DATACOM, P&D
“Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.” — Epitaph of a volunteer
next prev parent reply other threads:[~2018-11-07 1:25 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 [this message]
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
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=987477353.537443.1541553608738.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=kzak@redhat.com \
--cc=samuel.thibault@ens-lyon.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).