linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Adam Buchbinder <abuchbinder@google.com>, linux-btrfs@vger.kernel.org
Cc: dave@jikos.cz
Subject: Re: [PATCH 2/2] Remove a leading '+'.
Date: Fri, 13 Jun 2014 16:46:25 -0500	[thread overview]
Message-ID: <539B7131.9070005@redhat.com> (raw)
In-Reply-To: <1402695276-28104-2-git-send-email-abuchbinder@google.com>

On 6/13/14, 4:34 PM, Adam Buchbinder wrote:
> It was added in commit aab7f3ae3eb02fb7e8a6a31d7e2ada704a3dcd5e,
> most likely as a copy-pasteo.
> 
> Signed-off-by: Adam Buchbinder <abuchbinder@google.com>
> ---
>  btrfs-show-super.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/btrfs-show-super.c b/btrfs-show-super.c
> index f42cd15..ed0311f 100644
> --- a/btrfs-show-super.c
> +++ b/btrfs-show-super.c
> @@ -50,7 +50,7 @@ static void print_usage(void)
>  	fprintf(stderr, "\t-f : print full superblock information\n");
>  	fprintf(stderr, "\t-a : print information of all superblocks\n");
>  	fprintf(stderr, "\t-i <super_mirror> : specify which mirror to print out\n");
> -+	fprintf(stderr, "\t-F : attempt to dump superblocks with bad magic\n");
> +	fprintf(stderr, "\t-F : attempt to dump superblocks with bad magic\n");
>  	fprintf(stderr, "%s\n", BTRFS_BUILD_VERSION);
>  }
>  
> 

Whoa, git blame blames me, but that's not the patch I sent.  ;)

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

thanks,
-Eric


  reply	other threads:[~2014-06-13 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 21:34 [PATCH 1/2] Remove extra 'const' modifiers; they don't do anything Adam Buchbinder
2014-06-13 21:34 ` [PATCH 2/2] Remove a leading '+' Adam Buchbinder
2014-06-13 21:46   ` Eric Sandeen [this message]
2014-06-14 13:00     ` David Sterba

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=539B7131.9070005@redhat.com \
    --to=sandeen@redhat.com \
    --cc=abuchbinder@google.com \
    --cc=dave@jikos.cz \
    --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).