linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs pre-release 4.19.1-rc1
Date: Mon,  3 Dec 2018 17:47:12 +0100	[thread overview]
Message-ID: <20181203164712.15877-1-dsterba@suse.com> (raw)

Hi,

this is a pre-release of btrfs-progs, 4.19.1-rc1. There are build fixes, minor
update to libbtrfsutil and documentation updates.

The 4.19.1 release is scheduled to this Wednesday, +2 days (2018-12-05).

Changelog:
  * build fixes
    * big-endian builds fail due to bswap helpers clash
    * 'swap' macro is too generic, renamed to prevent build failures
  * libbtrfs
    * monor version update to 1.1.0
    * fix default search to top=0 as documented
    * rename 'async' to avoid future python binding problems
    * add support for unprivileged subvolume listing ioctls
    * added tests, API docs
  * other
    * lot of typos fixed
    * warning cleanups
    * doc formatting updates
    * CI tests against zstd 1.3.7

Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git

Shortlog:

David Sterba (7):
      btrfs-progs: kerncompat: rename swap to __swap
      btrfs-progs: README: add link to INSTALL
      btrfs-progs: docs: fix rendering of exponents in manual pages
      btrfs-progs: link to libbtrfsutil/README from the main README
      btrfs-progs: tests: pull zstd version 1.3.7 to the travis CI
      btrfs-progs: update CHANGES for v4.19.1
      Btrfs progs v4.19.1-rc1

Josh Soref (11):
      btrfs-progs: docs: fix typos in Documentation
      btrfs-progs: docs: fix typos in READMEs, INSTALL and CHANGES
      btrfs-progs: fix typos in Makefile
      btrfs-progs: tests: fix typos in test comments
      btrfs-progs: tests: fsck/025, fix typo in helpre name
      btrfs-progs: fix typos in comments
      btrfs-progs: fix typos in user-visible strings
      btrfs-progs: check: fix typo in device_extent_record::chunk_objectid
      btrfs-progs: utils: fix typo in a variable
      btrfs-progs: mkfs: fix typo in "multipler" variables
      btrfs-progs: fix typo in btrfs-list function export

Omar Sandoval (10):
      libbtrfsutil: use top=0 as default for SubvolumeIterator()
      libbtrfsutil: change async parameters to async_ in Python bindings
      libbtrfsutil: document qgroup_inherit parameter in Python bindings
      libbtrfsutil: use SubvolumeIterator as context manager in tests
      libbtrfsutil: add test helpers for dropping privileges
      libbtrfsutil: allow tests to create multiple Btrfs instances
      libbtrfsutil: relax the privileges of subvolume_info()
      libbtrfsutil: relax the privileges of subvolume iterator
      libbtrfsutil: bump version to 1.1.0
      libbtrfsutil: document API in README

Rosen Penev (3):
      btrfs-progs: kernel-lib: bitops: Fix big endian compilation
      btrfs-progs: task-utils: Fix comparison between pointer and integer
      btrfs-progs: treewide: Fix missing declarations


                 reply	other threads:[~2018-12-03 16:47 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=20181203164712.15877-1-dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@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).