All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kreijack@libero.it" <kreijack@libero.it>
To: <avbidder@fortytwo.ch>
Cc: linux-btrfs@vger.kernel.org
Subject: R: Re: [RFC] Move all btrfs command to only one command
Date: Fri, 22 Jan 2010 13:47:13 +0100 (CET)	[thread overview]
Message-ID: <7491720.68711264164433888.JavaMail.defaultUser@defaultHost> (raw)



>----Messaggio originale----
>Da: avbidder@fortytwo.ch
>Data: 22/01/2010 9.23
>A: <linux-btrfs@vger.kernel.org>
>Cc: "Goffredo Baroncelli"<kreijack@gmail.com>
>Ogg: Re: [RFC] Move all btrfs command to only one command
>
>Hi,
>
>I like this very much, I found myself wondering which program did what 
again 
>and again when I started to use btrfs, too.
>
>On Thursday 21 January 2010 20.29:26 Goffredo Baroncelli wrote:
>>        btrfs resize|-r [+/-]<newsize>[gkm]|max <filesystem>
>>                Resize the file system. If 'max' is passed, the filesystem
>>                will occupe all available space on the device.
>
>Switch the arguments, and if the 2nd is missing do what you propose for 
>"max".

I prefer that the switch still be before. But if it is missing, 'max' should 
be a reasonable default.
So the syntax becomes:

      btrfs resize|-r [[+/-]<newsize>[gkm]|max] <filesystem>
               Resize the file system. If '-r' is missing or 'max' is passed, 
the filesystem
               will occupe all available space on the device. 

>
>>         btrfs scan|-S [<device> [<device>..]
>>                 Scan all device for or the passed device for a btrfs
>> filesystem.
>
>This is the only that *migt* be sensible to have as a separate tool, if 
>"btrfs" ends up requiring additional runtime dependencies: the scan utility 
>should be small since it will need to be included in the initrd.

My command "btrfs" is only a front end which call library functions. It 
doesn't implement the scan engine.
But I agree that a "small" tool which performs the scanning only function is 
reasonable.

>-- 
>Protect your privacy - encrypt your email: http://fortytwo.ch/gpg/intro
>



                 reply	other threads:[~2010-01-22 12:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7491720.68711264164433888.JavaMail.defaultUser@defaultHost \
    --to=kreijack@libero.it \
    --cc=avbidder@fortytwo.ch \
    --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 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.