From: David Sterba <dave@jikos.cz>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: chris.mason@fusionio.com, dave@jikos.cz,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
ierdnah@gmail.com
Subject: Re: [PATCH v2] Btrfs: allow mount -o remount,compress=no
Date: Thu, 28 Jun 2012 17:40:37 +0200 [thread overview]
Message-ID: <20120628154037.GA28144@twin.jikos.cz> (raw)
In-Reply-To: <4FE95B45.8030909@arndnet.de>
On Tue, Jun 26, 2012 at 08:48:37AM +0200, Arnd Hannemann wrote:
> How show should we proceed to get above mentioned patch
> (or the similar patch from Andrei Popa) merged?
Josef picked the patch into btrfs-next, I see not problem to include it
in next merge window patchset.
david
next prev parent reply other threads:[~2012-06-28 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 19:46 [PATCH] Btrfs: allow mount -o remount,compress=no Arnd Hannemann
2012-04-06 10:22 ` David Sterba
2012-04-16 13:27 ` [PATCH v2] " Arnd Hannemann
2012-04-16 14:42 ` David Sterba
2012-06-26 6:48 ` Arnd Hannemann
2012-06-28 15:40 ` David Sterba [this message]
2012-07-13 15:19 ` Mitch Harder
2012-07-19 1:28 ` David Sterba
2012-07-19 19:31 ` Mitch Harder
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=20120628154037.GA28144@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=arnd@arndnet.de \
--cc=chris.mason@fusionio.com \
--cc=ierdnah@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).