linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas D Steeves <nsteeves@gmail.com>
To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: fix user-facing typos (affects 4.7.3 and devel)
Date: Mon, 26 Sep 2016 16:14:50 -0400	[thread overview]
Message-ID: <20160926201450.GA29587@DigitalMercury.dynalias.net> (raw)
In-Reply-To: <20160925012641.24339-1-nsteeves@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Sat, Sep 24, 2016 at 09:26:40PM -0400, Nicholas D Steeves wrote:
> Hi,
> 
> I found these with lintian (analysis tool for Debian packages) this
> evening, and hope this patch is well received :-)  The only bit I'm
> unsure about is the deletion of what looks like extra whitespace on
> the last changed line of the patch.
> 
> Cheers,
> Nicholas
> 
> Nicholas D Steeves (1):
>   Fix user-facing typos
> 
>  Documentation/btrfs-check.asciidoc  | 2 +-
>  Documentation/btrfs-device.asciidoc | 2 +-
>  Documentation/btrfs-man5.asciidoc   | 2 +-
>  Documentation/btrfs-scrub.asciidoc  | 2 +-
>  Documentation/btrfstune.asciidoc    | 2 +-
>  btrfs-convert.c                     | 2 +-
>  cmds-check.c                        | 6 +++---
>  7 files changed, 9 insertions(+), 9 deletions(-)
> 
> -- 
> 2.9.3
> 

P.S. The typos were found in btrfs-progs-v4.7.3, and this patch is
against David Sterba's github copy of the devel branch.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-09-26 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25  1:26 [PATCH] btrfs-progs: fix user-facing typos Nicholas D Steeves
2016-09-25  1:26 ` [PATCH] Fix " Nicholas D Steeves
2016-09-26 21:22   ` David Sterba
2016-09-26 20:14 ` Nicholas D Steeves [this message]

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=20160926201450.GA29587@DigitalMercury.dynalias.net \
    --to=nsteeves@gmail.com \
    --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).