From: David Nicol <davidnicol@gmail.com>
To: BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>
Subject: Re: Mark btrfsctl deprecated
Date: Mon, 25 Oct 2010 16:29:32 -0500 [thread overview]
Message-ID: <AANLkTimiuTM02Dnue_3NdC+uLbCMP9hEjfrp_4efFbGe@mail.gmail.com> (raw)
In-Reply-To: <22986774.2784821287748969875.JavaMail.defaultUser@defaultHost>
I am certainly not in a position to answer for Chris Mason, but I am
happy to share my response to the question, coming from a perspective
of being somewhat obsessive about not breaking back-compat.
Let's not. As I am certainly within the "lot of people" in question,
having just done exactly that, I found the two programs -- with very
different styles -- to not be much of a block, and providing two
examples instead of one of code that invokes an ioctl seems fine.
Ideally, everyone who needs to use an ioctl will simply write and
compile a C program that does what they need -- ha ha.
I see no reason to break legacy code (such as it is) that uses
btrfsctl instead of btrfs for a user-space tool to invoke ioctls.
Calling the tool "btrfs" is actually a little confusing.
On Fri, Oct 22, 2010 at 7:02 AM, Goffredo Baroncelli
<kreijack@libero.it> <kreijack@libero.it> wrote:
> Hi Chris,
>
> what do you think about marking deprecate the "btrfsctl" program ?
>
> A lot of people make patch involving both btrfs command and btrfsctl command,
> spending a lot of effort.
>
> Initially we can put a warning in the btrfctl command which suggest to use the
> btrfs command. and after XX month (six ?) we could remouve the command at all.
> The same for the other utilities like btrfs-show, btrfs-vol....
>
> Of course this is applicable if there is no evidence of regression of btrfs vs
> btrfsctl.
>
> Regards
> G.Baroncelli
next prev parent reply other threads:[~2010-10-25 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 12:02 Mark btrfsctl deprecated Goffredo Baroncelli <kreijack@libero.it>
2010-10-25 21:29 ` David Nicol [this message]
2010-10-26 17:32 ` Goffredo Baroncelli
2010-10-26 19:53 ` Chris Mason
2010-10-27 18:49 ` [RFC PATCH] Deprecate btrfsctl, btrfs-show, btrfs-vol 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=AANLkTimiuTM02Dnue_3NdC+uLbCMP9hEjfrp_4efFbGe@mail.gmail.com \
--to=davidnicol@gmail.com \
--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).