From: Eric Sandeen <sandeen@redhat.com>
To: Jon Nelson <jnelson@jamponi.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: minor patch to cmds-restore.c
Date: Fri, 19 Apr 2013 21:48:59 -0700 [thread overview]
Message-ID: <51721E3B.20905@redhat.com> (raw)
In-Reply-To: <CAKuK5J3LnB41=qKdDFrpQ2jPU+=fE2jPT-Da+NP3iBy8Xx8hmQ@mail.gmail.com>
On 4/19/13 7:11 PM, Jon Nelson wrote:
> The following is a minor patch to cmds-restore.c
>
Hi Jon - just a note -
When sending a patch like this, it's best to follow the standard
patch format, which closely mimics the kernel patch submission
guidelines:
Subject: [PATCH] btrfs-progs: <descriptive summary>
<longer description of change, if needed>
Signed-off-by: <you> <you@your.email.com>
---
<patch itself>
i.e. like:
Subject: [PATCH] btrfs-progs: fix btrfs restore command usage text
The built-in command help for btrfs restore was incorrect;
some options were missing and/or incorrect, and the destination
argument was not shown.
Signed-off-by: Jon Nelson <jnelson@jamponi.net>
---
That way it's clear to the reviewer as well as making the source
control history more descriptive.
Hum, it'd be nice to have it in the manpage too...
Thanks,
-Eric
> diff --git a/cmds-restore.c b/cmds-restore.c
> index c75e187..273c813 100644
> --- a/cmds-restore.c
> +++ b/cmds-restore.c
> @@ -917,14 +917,16 @@ out:
> }
>
> const char * const cmd_restore_usage[] = {
> - "btrfs restore [options] <device>",
> + "btrfs restore [options] <device> [destination]",
> "Try to restore files from a damaged filesystem (unmounted)",
> "",
> + "-l list roots",
> "-s get snapshots",
> "-v verbose",
> "-i ignore errors",
> "-o overwrite",
> - "-t tree location",
> + "-r <rootid> root location",
> + "-t <treeid> tree location",
> "-f <offset> filesystem location",
> "-u <block> super mirror",
> "-d find dir",
>
>
> --
> Jon
> Software Blacksmith
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-04-20 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 2:11 minor patch to cmds-restore.c Jon Nelson
2013-04-20 4:48 ` Eric Sandeen [this message]
2013-04-20 13:08 ` Jon Nelson
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=51721E3B.20905@redhat.com \
--to=sandeen@redhat.com \
--cc=jnelson@jamponi.net \
--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.