From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.29-rc
Date: Fri, 06 Feb 2009 16:51:07 -0500 [thread overview]
Message-ID: <1233957067.10366.0.camel@think.oraclecorp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0902060851270.3048@localhost.localdomain>
On Fri, 2009-02-06 at 08:53 -0800, Linus Torvalds wrote:
>
> On Fri, 6 Feb 2009, Chris Mason wrote:
> >
> > Here's the shortlog:
>
> Diffstats too, please.
>
Whoops, here we go:
fs/btrfs/Kconfig | 13 ++
fs/btrfs/async-thread.c | 60 +++++++-
fs/btrfs/ctree.c | 259 ++++++++++++++++++++++++++++--
fs/btrfs/ctree.h | 5 +-
fs/btrfs/disk-io.c | 16 ++-
fs/btrfs/extent-tree.c | 397 +++++++++++++++++++++++++++++++++++++++++------
fs/btrfs/extent_io.c | 39 ++---
fs/btrfs/extent_io.h | 16 ++-
fs/btrfs/inode.c | 57 ++++++-
fs/btrfs/locking.c | 208 ++++++++++++++++++++++--
fs/btrfs/locking.h | 6 +
fs/btrfs/ref-cache.c | 1 +
fs/btrfs/ref-cache.h | 1 -
fs/btrfs/tree-defrag.c | 1 +
fs/btrfs/tree-log.c | 4 +
fs/btrfs/volumes.c | 11 +-
fs/btrfs/xattr.c | 34 ++++-
fs/btrfs/xattr.h | 2 +
18 files changed, 996 insertions(+), 134 deletions(-)
This time around, there are actually lots of comments added.
-chris
next prev parent reply other threads:[~2009-02-06 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:22 [GIT PULL] Btrfs updates for 2.6.29-rc Chris Mason
2009-02-06 16:53 ` Linus Torvalds
2009-02-06 21:51 ` Chris Mason [this message]
2009-02-06 21:59 ` Linus Torvalds
2009-02-07 0:10 ` Chris Mason
2009-02-07 16:37 ` Linus Torvalds
2009-02-07 23:50 ` Chris Mason
2009-02-08 10:16 ` Kay Sievers
-- strict thread matches above, loose matches on Subject: below --
2009-02-13 20:25 Chris Mason
2009-02-26 15:09 Chris Mason
2009-02-26 15:11 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=1233957067.10366.0.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.