From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs-progs: Use named constants for common sizes
Date: Thu, 27 Jul 2017 21:02:12 +0000 (UTC) [thread overview]
Message-ID: <pan$9b8a8$c35443cf$d85bd4b7$f5299060@cox.net> (raw)
In-Reply-To: 1501143420-28062-2-git-send-email-nborisov@suse.com
Nikolay Borisov posted on Thu, 27 Jul 2017 11:17:00 +0300 as excerpted:
> diff --git a/convert/main.c b/convert/main.c
> index c56382e915fd..49ab829b5641 100644
> --- a/convert/main.c
> +++ b/convert/main.c
> @@ -1586,7 +1586,7 @@ next:
> * | RSV 1 | | Old | | RSV 2 | | Old | | RSV 3 |
> * | 0~1M | | Fs | | SB2 + 64K | | Fs | | SB3 + 64K |
> *
> - * On the other hande, the converted fs image in btrfs is a completely
> + * On the other hande, the converted fs image in btrfs is a completely
> * valid old fs.
> *
> * |<-----------------Converted fs image in btrfs-------------------->|
If you're going to kill the line-terminating space, you might as well
do the spell-correct in the same line:
s/hande/hand/
(Or avoid the noise of doing either. I'm not sure which the devs prefer.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-07-27 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 8:16 [PATCH 1/2] btrfs-progs: Use already defined BTRFS_BLOCK_GROUP_PROFILE_MASK Nikolay Borisov
2017-07-27 8:17 ` [PATCH 2/2] btrfs-progs: Use named constants for common sizes Nikolay Borisov
2017-07-27 21:02 ` Duncan [this message]
2017-08-22 14:31 ` David Sterba
2017-08-22 14:31 ` 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='pan$9b8a8$c35443cf$d85bd4b7$f5299060@cox.net' \
--to=1i5t5.duncan@cox.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 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).