From: David Sterba <dsterba@suse.cz>
To: chris.mason@fusionio.com
Cc: linux-btrfs@vger.kernel.org
Subject: [GIT PULL] btrfs-progs: Handful of fixes for 0.20-rc1
Date: Tue, 2 Oct 2012 13:27:07 +0200 [thread overview]
Message-ID: <20121002112707.GH4545@ds.suse.cz> (raw)
Hi Chris,
please pull a few fixes to the 0.20-rc series, these are easy to review and fix
problems that people reported. There are more fixes in the mailinglist, but
they do not IMHO fit current -rc period, the crowd is waiting for 0.20.
git://repo.or.cz/btrfs-progs-unstable/devel.git for-chris/rc2
Based on top of master commit d88f33152f3d69240b6c690188b5d832a1663c07.
Thanks.
---
btrfs-vol.c | 3 ++-
btrfsck.c | 2 +-
cmds-device.c | 3 ++-
cmds-qgroup.c | 3 +++
man/mkfs.btrfs.8.in | 3 ++-
mkfs.c | 23 ++++++++++-------------
utils.c | 14 ++++----------
utils.h | 6 ++----
8 files changed, 26 insertions(+), 31 deletions(-)
---
David Sterba (3):
btrfs-progs: mkfs: rename nodiscard option to K
btrfs-progs: mkfs: create root directory with 755 permissions
btrfs-progs: fsck: understand the -s option
Josef Bacik (1):
Btrfs-progs: only enforce a maximum size if we specify one
Tsutomu Itoh (1):
Btrfs-progs: fix arguments check of qgroup limit
next reply other threads:[~2012-10-02 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 11:27 David Sterba [this message]
2012-10-02 23:48 ` [GIT PULL] btrfs-progs: Handful of fixes for 0.20-rc1 Chris Mason
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=20121002112707.GH4545@ds.suse.cz \
--to=dsterba@suse.cz \
--cc=chris.mason@fusionio.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).