From: Josef Bacik <jbacik@fb.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel BUG: btrfs send - Incremental backup
Date: Wed, 12 Mar 2014 13:07:27 -0400 [thread overview]
Message-ID: <5320944F.9060106@fb.com> (raw)
In-Reply-To: <1534308.rS2sq7rkIX@tethys>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/12/2014 04:20 AM, Swâmi Petaramesh wrote:
> Hi Josef,
>
> I'm afraid I will not have the time to perform the kernel
> compilations and tests you request in the coming days. I'm sorry
> but I will really be 120% overloaded already...
>
>
That's fine, if you get a chance to then great, if not that's fine
too. Thanks,
Josef
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTIJRPAAoJEANb+wAKly3BL0gP/2bFqad7MLB/2v3qWBOreWBC
mpuMMQZjPMqqqA5JZxyImr5K6NYJJjdNGH4ZganCP+WUAHOSPjSuIu3TLTkMt6IW
UEXEkXcSowLXof+2uHglocz0NDK+XOQnzSKAvRRjlyrCN5dvR2O9UG9aMcP4H05L
KJ8a1h+Ic8A+w37roako33+DKYVJrjBiXDAQy7Cw1+dxLyAlARsNbv5am7e93uK3
NZV19K6q3WgrzbbK25v5Z3Qq4QH3GJRD3gfJNwbtoiSKOuphZhcpf85P4JZyT3G0
/xOHfPy4+LOibj/WXUfm/xu3jVgjrSaJi+wtmQdA6DCw01tByNGYWervPEg8BC5e
nkjcy/4JdMKgWe6h3UZLXTWjGa2e6wa6kfvac7gkduwphnA8U5kPodx+LMT6xPZq
kCtZ3o7E19alnyscz6/0+3GEW4uYNIGZv1BjBc0fCLJf3LzWCiBPaafkuakLJQkJ
bNXnfttk/REEVqQ/j7gOF/rVDt1S8uTuEmC8eHxImFSeTkJQ4KYUuX5ujb+wVbrv
oPh12EDYSQUDWTfqocANE5lPPVM4iscJ7ZQ3Ae3TTWUtF3GnPMTYAt2at2bQChDK
TcNdgONs+4g3W6/JZVn4RypHe+qH7rg8Mu2hGKFq9MM2565NCBBsp6Jfe9sg3e84
bNMGf0EU9zFWV5fxfCu8
=KVKy
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-03-12 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 7:35 Kernel BUG: btrfs send - Incremental backup Swâmi Petaramesh
2014-03-10 2:16 ` quwenruo
2014-03-10 7:25 ` Swâmi Petaramesh
2014-03-10 7:34 ` quwenruo
2014-03-10 8:30 ` Swâmi Petaramesh
2014-03-11 17:12 ` Josef Bacik
2014-03-12 8:20 ` Swâmi Petaramesh
2014-03-12 17:07 ` Josef Bacik [this message]
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=5320944F.9060106@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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.