On 3/1/13 4:10 AM, Anand Jain wrote:
> Signed-off-by: Anand Jain <anand.jain@xxxxxxxxxx>
Revieed-by: Eric Sandeen <sandeen@xxxxxxxxxx>
But the curious side of me wonders how it got this way.
commit e43cc461550130494194201037590a2b1f0f6880
Author: Ian Kumlien <pomac@xxxxxxxxxx>
Date: Fri Feb 8 01:37:02 2013 +0100
Btrfs-progs: add restore command to btrfs
added the usage text below, but didn't change the getopt
or add code to handle them.
No idea where it came from, it wasn't in the standalone
restore either. *shrug* I guess nothing got lost.
-Eric
> ---
> cmds-restore.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/cmds-restore.c b/cmds-restore.c
> index 9385042..4a14f93 100644
> --- a/cmds-restore.c
> +++ b/cmds-restore.c
> @@ -763,10 +763,6 @@ const char * const cmd_restore_usage[] = {
> "-f <offset> filesystem location",
> "-u <block> super mirror",
> "-d find dir",
> - "-r <num> root objectid",
> - "-c ignore case in regular expression",
> - "-m <regexp> regular expression to match",
> - "-l list roots",
> NULL
> };
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
