From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Updated btrfs-next
Date: Wed, 11 Dec 2013 14:15:11 -0500 [thread overview]
Message-ID: <52A8B9BF.9030707@fb.com> (raw)
Hello,
I just updated and pushed btrfs-next, if it is missing something let me
know. I had to kick out the printk formatting patch because it didn't
compile and I didn't take Miao's background enospc flushing stuff since
some of it didn't apply and 5/5 hasn't been updated to force waiting on
background flushers. Let me know if I missed anything else. Thanks,
Josef
next reply other threads:[~2013-12-11 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 19:15 Josef Bacik [this message]
2013-12-12 9:55 ` Updated btrfs-next Anand Jain
2013-12-12 13:08 ` David Sterba
2013-12-12 14:46 ` Chris Mason
2013-12-12 18:17 ` David Sterba
2013-12-12 20:17 ` Frank Holton
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=52A8B9BF.9030707@fb.com \
--to=jbacik@fb.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 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.