All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Sheriff Esseson <sheriffesseson@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: design: Fix typo
Date: Tue, 30 Jul 2019 07:41:51 -0700	[thread overview]
Message-ID: <20190730144151.GQ1561054@magnolia> (raw)
In-Reply-To: <20190730123648.GA20126@localhost>

On Tue, Jul 30, 2019 at 01:36:48PM +0100, Sheriff Esseson wrote:
> Replace "possible" with "possibly" and improve the flow of the phrase.
> 
> Signed-off-by: Sheriff Esseson <sheriffesseson@gmail.com>

Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
>  design/XFS_Filesystem_Structure/overview.asciidoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  mode change 100644 => 100755 design/XFS_Filesystem_Structure/overview.asciidoc
> 
> diff --git a/design/XFS_Filesystem_Structure/overview.asciidoc b/design/XFS_Filesystem_Structure/overview.asciidoc
> old mode 100644
> new mode 100755
> index d15b50a..7628a7d
> --- a/design/XFS_Filesystem_Structure/overview.asciidoc
> +++ b/design/XFS_Filesystem_Structure/overview.asciidoc
> @@ -28,7 +28,7 @@ record.  Both forks associate a logical offset with an extent of physical
>  blocks, which makes sparse files and directories possible.  Directory entries
>  and extended attributes are contained inside a second-level data structure
>  within the blocks that are mapped by the forks.  This structure consists of
> -variable-length directory or attribute records and possible a second B+tree to
> +variable-length directory or attribute records and, possibly, a second B+tree to
>  index these records.
>  
>  XFS employs a journalling log in which metadata changes are collected so that
> -- 
> 2.22.0
> 

      reply	other threads:[~2019-07-30 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 12:36 [PATCH] xfs: design: Fix typo Sheriff Esseson
2019-07-30 14:41 ` Darrick J. Wong [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=20190730144151.GQ1561054@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sheriffesseson@gmail.com \
    /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.