From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Mason <chris.mason@oracle.com>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] btrfs-progs: first slice of integration branch
Date: Thu, 30 Jun 2011 21:22:45 +0100 [thread overview]
Message-ID: <20110630202245.GA4352@carfax.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2756 bytes --]
Hi, Chris,
I've done a more detailed examination of the patches in my
integration branch of btrfs-progs, and this is the set of small and
generally inoffensive/uncontroversial patches from that stack. I've
reviewed them all, and didn't see anything horribly wrong in there.
Since I was looking for the low-hanging fruit in getting this first
lot out, I've omitted the scrub, balance management, and chunk tree
recovery features in this round -- they'll be along when I've had a
chance to review the longer additions in more detail.
The series is based on the tmp branch, and can be pulled from:
http://git.darksatanic.net/repo/btrfs-progs-unstable.git/ for-chris
Hugo.
Andreas Philipp (5):
Added support for an additional ioctl.
Add support for read-only subvolumes.
Support the new parameters in do_clone(int argc, char** argv).
Test the additional ioctl.
Updated manpage for btrfs subvolume snapshot.
Anton Blanchard (1):
btrfs-progs: cast u64 to long long to avoid printf warnings
Arne Jansen (3):
btrfs-map-logical: usage update
btrfs progs: fix extra metadata chunk allocation in --mixed case
btrfs-map-logical: segfaults when no output file is given
Chris Ball (1):
Fix unused-but-set errors in gcc-4.6
Fajar A. Nugraha (1):
make "btrfs filesystem label" command actually work
Hubert Kario (2):
add advanced use of --help to help message
add detailed help messages to btrfs command
Hugo Mills (2):
btrfs-progs: Fix over-sized limit on buffer
mkfs.btrfs: Fix compilation errors with gcc 4.6
Jan Schmidt (1):
mkfs should initialize unused fields properly
Kamble, Nitin A (1):
make btrfs cross compilation friendly
Sergei Trofimovich (8):
btrfs-convert: fix typo: 'all inode' -> 'all inodes'
mkfs.btrfs: fail on scandir error (-r mode)
mkfs.btrfs: return some defined value instead of garbage when lookup checksum
mkfs.btrfs: fix symlink names writing
mkfs.btrfs: write zeroes instead on uninitialized data.
mkfs.btrfs: free buffers allocated by pretty_sizes
mkfs.btrfs: fix memory leak caused by 'scandir()' calls
mkfs.btrfs: fix error text in '-r' mode
Stephane Chazelas (1):
incorrect argument checking for "btrfs sub snap -r"
Tsutomu Itoh (1):
btrfs-progs: setting of time to the root directory
cwillu (1):
Btrfs-progs: Correct path munging in bcp
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- What's a Nazgûl like you doing in a place like this? ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2011-06-30 20:22 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=20110630202245.GA4352@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=chris.mason@oracle.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).