From: Hugo Mills <hugo@carfax.org.uk>
To: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Integration branch updated
Date: Sun, 26 Jun 2011 22:10:22 +0100 [thread overview]
Message-ID: <20110626211022.GA24675@carfax.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
I've just updated the btrfs-progs integration branch I've been
keeping. Not a huge amount new since last time:
Andreas Philipp (1):
print parent ID in btrfs subvolume list
Goffredo Baroncelli (1):
Scan the devices listed in /proc/partitions
Hugo Mills (1):
mkfs.btrfs: Fix compilation errors with gcc 4.6
Zhong, Xin (1):
btrfs-progs: Improvement for making btrfs image from source directory.
cwillu (1):
Btrfs-progs: Correct path munging in bcp
I've also re-worked my balance-management patches to deal with a
few oddities in the ordering of the help output, and the parameter
counts for the various balance commands.
You can get the latest version from:
http://git.darksatanic.net/repo/btrfs-progs-unstable.git/ integration-20110626
Hugo.
--
=== 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
--- "I am the author. You are the audience. I outrank you!" ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2011-06-26 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 21:10 Hugo Mills [this message]
2011-06-27 12:43 ` Integration branch updated David Sterba
2011-06-27 13:03 ` Andreas Philipp
2011-06-27 14:45 ` Hugo Mills
2011-07-01 10:21 ` [PATCH v2] print parent ID in btrfs suvolume list Andreas Philipp
2011-07-02 7:55 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 19:35 integration branch updated 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=20110626211022.GA24675@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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).