From: Karel Zak <kzak@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: [ANNOUNCE] util-linux v2.23.1 (stable)
Date: Tue, 28 May 2013 12:29:41 +0200 [thread overview]
Message-ID: <20130528102941.GA20866@x2.net.home> (raw)
The util-linux stable release v2.23.1 is available at
ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.23
Feedback and bug reports, as always, are welcomed.
Karel
Util-linux 2.23.1 Release Notes
===============================
blkid:
- fix typo in ID_FS_AMBIVALEN= [Karel Zak]
build-sys:
- add --disable-setterm [Karel Zak]
- always check for setns() and unshare() libs functions [Karel Zak]
- use -Wno-clobbered for some BSD crap [Karel Zak]
chcpu:
- clean up error messages [Karel Zak]
lib/loopdev:
- fix loopcxt_check_size() to work with blkdevs [Karel Zak]
lib/tty:
- don't hardcode terminal fd in get_terminal_name() [Karel Zak]
- fix get_terminal_name() usage, cleanup code [Karel Zak]
libblkid:
- add ReFS magic string [Karel Zak]
- fix blkid_parse_tag_string() to ignore incomplete tags [Karel Zak]
libfdisk:
- do not use va_list in the Ask API [Karel Zak]
libmount:
- don't ignore root fs on umount -a [Karel Zak]
- use MS_SILENT for /{proc,etc}/filesystems [Karel Zak]
losetup:
- use warn_size() for regular files only [Karel Zak]
lsblk:
- add SERIAL column [Karel Zak]
po:
- merge changes [Karel Zak]
- update nl.po (from translationproject.org) [Benno Schulenberg]
- update vi.po (from translationproject.org) [Trần Ngọc Quân]
- update zh_CN.po (from translationproject.org) [Wylmer Wang]
sfdisk:
- don't call BLKRRPART for non-block devices [Karel Zak]
sulogin:
- clean up error messages [Karel Zak]
tests:
- new warning fix [Gilles Espinasse]
- standard SEE ALSO section of man pages [Mike Frysinger]
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
reply other threads:[~2013-05-28 10:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130528102941.GA20866@x2.net.home \
--to=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).