From: Gene Czarcinski <gene@czarc.net>
To: dsterba@suse.cz
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
Date: Fri, 18 Jan 2013 09:16:00 -0500 [thread overview]
Message-ID: <50F95920.406@czarc.net> (raw)
In-Reply-To: <20130117174721.GD22785@twin.jikos.cz>
On 01/17/2013 12:47 PM, David Sterba wrote:
> Hi Chris,
>
> please pull a few more fixes to the 0.20-rc series. I have reviewed and
> verified them where possible. There are the long awaited ARM fixes, help
> updates and unsorted code fixes.
>
> git://repo.or.cz/btrfs-progs-unstable/devel.git for-chris
>
> Based on top of master commit
> 91d9eec1ff044394f2b98ee7fcb76713dd33b994
>
> Thanks.
> david
>
> ---
> btrfs-list.c | 69 +++++++++++++++++++++++++-----------------------------
> btrfsck.c | 3 +-
> cmds-filesystem.c | 26 --------------------
> cmds-inspect.c | 5 ++-
> cmds-receive.c | 4 ++-
> cmds-scrub.c | 4 ++-
> cmds-send.c | 9 ++++++-
> convert.c | 5 +++
> ctree.h | 8 ++++--
> debug-tree.c | 10 +++++++
> disk-io.c | 13 ++++++++--
> kerncompat.h | 12 +++++++++
> man/btrfs.8.in | 4 ---
> mkfs.c | 35 ++-------------------------
> restore.c | 7 +++--
> utils.c | 48 +++++++++++++++++++++++++++++++++++++
> utils.h | 2 +
> version.sh | 2 -
> volumes.c | 8 +++---
> 19 files changed, 159 insertions(+), 115 deletions(-)
> ---
> Alex Lyakas (1):
> btrfs-progs: Receive: preserve ownership for symlinks, by using 'lchown'
>
> Arne Jansen (1):
> Btrfs-progs: fix unaligned accesses
>
> David Sterba (2):
> btrfs-progs: do not send stream into a terminal
> btrfs-progs: ignore -a option in mkfs
>
> Goffredo Baroncelli (3):
> Move parse_size() to utils.[hc]
> parse_size(): replace atoll() with strtoull()
> parse_size(): add new suffixes
>
> Kenji Okimoto (3):
> btrfs-progs: plug a memory leak reported by cppcheck
> btrfs-progs: check malloc() result
> btrfs-progs: plug memory leaks in btrfs_scan_one_dir() reported by cppcheck.
>
> Lluis Batlle i Rossell (1):
> btrfs-progs: Fix getopt on arm platforms
>
> Sergei Trofimovich (1):
> version.sh: fix version when built from tarball
While you are about it, how about adding in this fix from Dieter Ries to
fix version a little more:
http://article.gmane.org/gmane.comp.file-systems.btrfs/20069
>
> Simon Xu (2):
> btrfs-progs: remove "device show" from btrfs man page
> btrfs-progs: remove '-h' from btrfs man page
>
> Wade Cline (1):
> Btrfs-progs: Fix compiler warnings on PPC64
>
> Wang Sheng-Hui (3):
> btrfs-progs: add -V description in print_usage
> btrfs-progs: update usage description for debug-tree.c
> btrfs-progs: print the right mount checking info in restore.c
>
> Zach Brown (1):
> btrfs-progs: fix 32bit int/pointer cast warnings
>
>
next prev parent reply other threads:[~2013-01-18 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:47 [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1 David Sterba
2013-01-17 17:51 ` Chris Mason
2013-01-18 17:32 ` Goffredo Baroncelli
2013-01-18 14:16 ` Gene Czarcinski [this message]
2013-01-18 14:44 ` David Sterba
2013-01-18 15:49 ` Gene Czarcinski
2013-01-18 15:55 ` Hugo Mills
2013-01-18 16:48 ` Gene Czarcinski
2013-01-18 15:33 ` Gene Czarcinski
2013-01-18 17:22 ` David Sterba
2013-01-18 21:02 ` Gene Czarcinski
2013-01-21 10:50 ` David Sterba
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=50F95920.406@czarc.net \
--to=gene@czarc.net \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.