From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Gene Czarcinski <gene@czarc.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: remove btrfsctl, btrfs-show and btrfs-vol from default build
Date: Fri, 25 Jan 2013 16:49:59 +0100 [thread overview]
Message-ID: <5102A9A7.2000407@giantdisaster.de> (raw)
In-Reply-To: <5102A571.8030608@redhat.com>
On Fri, 25 Jan 2013 09:32:01 -0600, Eric Sandeen wrote:
> On 1/25/13 5:57 AM, Gene Czarcinski wrote:
>> On 06/08/2012 02:00 PM, Stefan Behrens wrote:
>>> Remove btrfsctl, btrfs-show and btrfs-vol from "all" target of Makefile.
>
> TBH, unless there are objections, I'd rather remove the source files as well.
>
> Having unbuilt source code lying around is potentially even more confusing.
>
> I'd at least move it to a deprecated/ subdir or something, but it'll only
> fester and die there as well. I'd just remove it, if it's time to do so.
Yes, right. Half a year ago, this was a first attempt from me to start a
discussion on this topic. But I agree that the removal of the sources
and the removal in the Makefile should be made in one commit.
Unfortunately Suse is still needing these old files as David wrote.
> Are they fully deprecated? Is there anything these tools do that btrfs
> does not?
Yes (fully deprecated for 2 years). No (the unified btrfs tool is a full
replacement).
next prev parent reply other threads:[~2013-01-25 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 18:00 [PATCH] Btrfs-progs: remove btrfsctl, btrfs-show and btrfs-vol from default build Stefan Behrens
2013-01-25 11:57 ` Gene Czarcinski
2013-01-25 15:32 ` Eric Sandeen
2013-01-25 15:49 ` Stefan Behrens [this message]
2013-01-28 3:03 ` Anand Jain
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=5102A9A7.2000407@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=gene@czarc.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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.