From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Allow for quick removing of btrfs signature from block device
Date: Tue, 1 May 2012 14:43:37 +0200 [thread overview]
Message-ID: <20120501124337.GA21063@mother.jarsat.pl> (raw)
In-Reply-To: <1335875886-12087-1-git-send-email-kario@wit.edu.pl>
On Tue, May 01, 2012 at 02:38:01PM +0200, Hubert Kario wrote:
> This patch series adds `btrfs device zero super <dev>` command to rem=
ove the
> btrfs signature from the device as well as fix few minor problems in
> btrfs_prepare_device function.
Shouldn't you rather extend =E2=80=9Cwipefs=E2=80=9D from util-linux?
--=20
Tomasz Torcz 72->=
| 80->|
xmpp: zdzichubg@chrome.pl 72->=
| 80->|
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-01 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 12:38 [PATCH v2 0/5] Allow for quick removing of btrfs signature from block device Hubert Kario
2012-05-01 12:43 ` Tomasz Torcz [this message]
2012-05-01 13:37 ` Hubert Kario
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=20120501124337.GA21063@mother.jarsat.pl \
--to=tomek@pipebreaker.pl \
--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 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).