From: Goffredo Baroncelli <kreijack@inwind.it>
To: linux-btrfs@vger.kernel.org
Cc: Stefan Behrens <sbehrens@giantdisaster.de>
Subject: [PATCH][btrfs-progs] Removing btrfsctl, btrfs-vol, btrfs-show
Date: Sat, 9 Jun 2012 08:24:18 +0200 [thread overview]
Message-ID: <1339223060-6256-1-git-send-email-kreijack@inwind.it> (raw)
With the commit 002d021c (committed October 2011)
btrfsctl, btrfs-vol, btrfs-show were declared deprecated.
The last patches related to these commands are dated December 2010.
These tools are replaced by the "btrfs" tool in all the
functionality.
Stefan Behrens yesterday issued a patch which removes these programs
from Makefile. I think that it is a time to remove these program at all.
You can pull this patch also from
http://cassiopea.homelinux.net/git/btrfs-progs-unstable.git
branch
remove-old
BR
G.Baroncelli
next reply other threads:[~2012-06-09 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 6:24 Goffredo Baroncelli [this message]
2012-06-09 6:24 ` [PATCH] Removing btrfsctl, btrfs-vol, btrfs-show Goffredo Baroncelli
2012-06-10 8:46 ` Chris Samuel
2012-06-10 20:49 ` Goffredo Baroncelli
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=1339223060-6256-1-git-send-email-kreijack@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).