public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: kreijack@inwind.it
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Re: New btrfs command pushed into the btrfs-progs subvol branch - commands
Date: Thu, 11 Mar 2010 22:27:12 -0500	[thread overview]
Message-ID: <20100312032712.GC3035@think> (raw)
In-Reply-To: <201003112244.31375.kreijack@inwind.it>

On Thu, Mar 11, 2010 at 10:44:21PM +0100, Goffredo Baroncelli wrote:
> Hi Chris,
> 
> I updated my git repository. You can pull from 
> 
> git pull http://cassiopea.homelinux.net/git/btrfs-command.git mlc-subvol
> 
> (branch mlc-subvol, commit e59135a27dc1fde6acc4fb198499be2b6cbd9f6f)
> 
> $ git diff remotes/origin/subvol | diffstat
>  btrfs-list.c   |   15 +++--
>  btrfs.c        |   56 +++++++++++++++++-
>  btrfs_cmds.c   |   84 +++++++++++++++++-----------
>  btrfs_cmds.h   |    1 
>  man/btrfs.8.in |  150 +++++++++++++++++++++++++++++++++++++++++++++[...]
>  5 files changed, 283 insertions(+), 43 deletions(-)
> 
> 
> As you requested I update the parser in order set the argv[0] argument as the 
> program name + the verb. For example if I do
> 
> 	$ btrfs dev add
> 
> the argv[0] will be equal to "btrfs device add". I hope that is what you 
> requested.

Great.

> 
> Due to this change I update all the commands in order to evaluate the 
> arguments from argv[1] and not from argv[0] anymore. (I update also your 
> do_defrag() function)
> 
> Also because I implemented that already the week ago:
> - I made some small modification to btrfs-list.c in order to be more friendly 
> in case of error (replace some "exit(2)" with "return -ERR")
> - I implemented the command "btrf subvolume set-default"

Wonderful.  I've rebased this and put it into the subvol branch.  I
think I got all the commits and differences.  The big reason for the
rebase is to avoid the small string of single liner fixup commits.
If you have other work pending I'm happy to rebase it in, otherwise
please try to work against my subvol branch.

Thanks again!

-chris


  reply	other threads:[~2010-03-12  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 18:54 New btrfs command pushed into the btrfs-progs subvol branch - commands Chris Mason
2010-03-11 19:03 ` Goffredo Baroncelli
     [not found]   ` <20100311190828.GN6509@think>
2010-03-11 21:44     ` [PATCH 1/2] " Goffredo Baroncelli
2010-03-12  3:27       ` Chris Mason [this message]
2010-03-12 17:06         ` Goffredo Baroncelli
2010-03-11 21:44     ` [PATCH 2/2] Re: New btrfs command pushed into the btrfs-progs subvol branch - man pages 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=20100312032712.GC3035@think \
    --to=chris.mason@oracle.com \
    --cc=kreijack@inwind.it \
    --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