From: Karel Zak <kzak@redhat.com>
To: Goffredo Baroncelli <kreijack@inwind.it>
Cc: util-linux@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
Chris Murphy <lists@colorremedies.com>
Subject: Re: [PATCH][v2] Btrfs: wipe all the superblock [redhat bugzilla 889888]
Date: Thu, 10 Jan 2013 11:44:47 +0100 [thread overview]
Message-ID: <20130110104447.GC593@x2.net.home> (raw)
In-Reply-To: <50EDDDC3.10407@inwind.it>
On Wed, Jan 09, 2013 at 10:14:43PM +0100, Goffredo Baroncelli wrote:
> libblkid/src/superblocks/btrfs.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2013-01-10 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 21:14 [PATCH][v2] Btrfs: wipe all the superblock [redhat bugzilla 889888] Goffredo Baroncelli
2013-01-10 10:44 ` Karel Zak [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=20130110104447.GC593@x2.net.home \
--to=kzak@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=util-linux@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).