linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [ANNOUNCE] util-linux v2.27.1
Date: Mon, 2 Nov 2015 12:08:47 +0100	[thread overview]
Message-ID: <20151102110754.GH19508@ws.net.home> (raw)

The util-linux release v2.27.1 is available at

  ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.27

Feedback and bug reports, as always, are welcomed.

    Karel


util-linux 2.27.1 Release Notes
===============================

bash-completion:
   - curly brace missed for findmnt  [Alexander Kuleshov]
docs:
   - update AUTHORS file  [Karel Zak]
fdisk:
   - fix -N internal return code  [Karel Zak]
   - to recognize Intel Rapid Start hibernation partition  [Jörg Jenderek]
   - to recognize partition type 0xEA (Rufus)  [Jörg Jenderek]
include/pt-mbr-partnames:
   - remove '|' from partition type name  [Karel Zak]
ipcs:
   - fix ipc_sem_get_limits()  [Karel Zak]
lib/sysfs:
   - make sysfs_get_devname()/blkid_devno_to_wholedisk() more robust  [Karel Zak]
libblkid:
   - (promise raid) cleanup code  [Karel Zak]
   - make XFS Log visible for wipefs  [Karel Zak]
libfdisk:
   - (gpt) control ranges in set_partition  [Karel Zak]
   - add more debug message to resize code  [Karel Zak]
   - fix partition move/resize code  [Karel Zak]
libmount:
   - (monitor) don't check for regular mtab  [Karel Zak]
   - (monitor) remove unnecessary epoll EPOLLPRI  [Karel Zak]
   - fix uid= and gid= translation  [Karel Zak]
   - follow docs with parse-error callback return code  [Karel Zak]
libuuid:
   - fix buffer overflow with long paths  [Karel Zak]
logger:
   - fix messages separation on UNIX socket  [Karel Zak]
mount, umount, swapon, fsck, lsblk, findmnt:
   - ignore malformed lines  [Karel Zak]
po:
   - merge changes  [Karel Zak]
   - update cs.po (from translationproject.org)  [Petr Písař]
   - update de.po (from translationproject.org)  [Philipp Thomas]
   - update pt_BR.po (from translationproject.org)  [Rafael Ferreira]
   - update ru.po (from translationproject.org)  [Evgeniy Yakushev]
   - update zh_CN.po (from translationproject.org)  [Wylmer Wang]
script:
   - be pedantic and use "%"SCNi64  [Karel Zak]
   - don't assume that time_t is compatible with long  [Isaac Dunham]
tests:
   - add missing files  [Karel Zak]
   - replace username with tag in logger test  [Karel Zak]
   - update and extend logger tests  [Karel Zak]
uuidd:
   - improve socket activation error messaging  [Sami Kerola]
zramctl:
   - fix lists of the all devices  [Karel Zak]


-- 
 Karel Zak  <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
 http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2015-11-02 11:08 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=20151102110754.GH19508@ws.net.home \
    --to=kzak-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).